HTTP header cache-control

[nicolasiensen]

I've noticed that the implementation of this polyfill differs from the implementation of EventSource by Google Chrome in the header of the request made to the SSE server.

When using the built-in Google Chrome EventSource implementation, the request does not include the cache-control HTTP header, whoever, when using the polyfill, this attribute is included.

The problem of this, in my case, was that my SSE server was not whitelisting this header, making all the SSE requests coming from clients using the polyfill to be rejected with a CORS error.

Is the cache-control attribute part of the EventSource specification? Should we omit it from the requests made with the polyfill?

[Reljod]

I'm facing the same issue as well. I'm hoping to see this being acknowledged.