[Bug 18796] HTTP 204 not specified

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18796

--- Comment #3 from Karl Dubost <karl+w3c@la-grange.net> ---
The "204" answer is implicited included in this section 5 sentence:

"Any other HTTP response code not listed here must cause the user agent to fail
the connection." 

Though 204 has no specific meaning in the context of server sent events because
in fact any kind of 2** code will terminate the connection but "200 with the
right mime-type".

Maybe I would expect in the intro more something along 

"A client could be told to stop reconnecting using the HTTP 204 No Content
response code (but not exclusively)."


Hixie, Art, I can live with it. Thanks for considering the bug.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.