https://www.w3.org/Bugs/Public/show_bug.cgi?id=22997
Ian 'Hixie' Hickson <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Ian 'Hixie' Hickson <[email protected]> --- The spec says: # Event streams in this format must always be encoded as UTF-8. # Streams must be decoded using the UTF-8 decode algorithm. ..and of the "charset" parameter: # The parameter's value must be "utf-8". This parameter serves no purpose; it # is only allowed for compatibility with legacy servers I don't really know how else to say this. Nothing in the spec mentions firing 'error' for EventSource if the charset="" is wrong (not UTF-8). In fact it explicitly says: # HTTP 200 OK responses with a Content-Type header specifying the type # text/event-stream, ignoring any MIME type parameters, must be processed # line by line as described below. (Notice the part that says "ignoring any MIME type parameters".) I've added yet more text to the intro, just in case, but... -- You are receiving this mail because: You are on the CC list for the bug.
