On Mon, 4 Jul 2011, Anne van Kesteren wrote: > I noticed Ian updated the specification, but it seems current > implementations differ quite wildly. E.g. Gecko happily ignores > > Content-Type: text/event-stream;charset=tralala > > as does Opera instead of closing the connection. Chrome bites, but happily > ignores > > Content-Type: text/event-stream;tralala > > along with Opera and Gecko. Safari 5.0.5 bites on that however and also on > charset=tralala. All browsers seem to allow (note the trailing semi-colon): > > Content-Type: text/event-stream; > > Are we sure we want this strict checking of media type parameters? I > always thought the media type itself was what strict checking should be > done upon, but that its parameters were extension points, not points of > failure.
Fair enough. I've changed the spec to ignore parameters on text/event-stream. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
