[whatwg] EventSource - Handling a charset in the content-type header
julien.chaffraix at gmail.com
Wed Mar 23 21:52:02 PDT 2011
the EventSource specification states the current content-type header
should match the string "text/event-stream". However following some
bugs opened inside the WebKit project , we relaxed the content-type
check to ignore any specified charset as it confused developers and
can potentially break existing servers that automatically send a
charset as part of the response .
We are currently revisiting our approach and our current take would be
to allow a mime-type of "text/event-stream" with an optional
charset="UTF-8". No other charset would be allowed as UTF-8 is the
only encoding supported by the standard.
We are not set-up on the best way to fix this and would like to reach
a consensus before correcting our existing behavior so that the
specification is clarified on this point. Also note that the same
problem exists for the application cache .
More information about the whatwg