[Bug 18796] New: HTTP 204 not specified

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

           Summary: HTTP 204 not specified
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Server-Sent Events (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: karl+w3c@la-grange.net
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


In the non normative document introduction "Editor's Draft 26 August 2012"
http://dev.w3.org/html5/eventsource/

it is mentionned:

>Clients will reconnect if the connection is closed; a client can be told to stop reconnecting using the HTTP 204 No Content response code.

This is the only moment in the document where this scenario is being given as a
possibility for "blocking the reconnection". A scenario could be

1. Event Stream being opened by the client
2. The server could drop the connection
3. The client tries to reconnect
4. The server replied 204
5. The client definitely drops the connection

There is a discussion on HTTP code in 5. Processing Model but which basically
says that 

>Any other HTTP response code not listed here, and any network error that prevents the HTTP connection from being established in the first place (e.g. DNS errors), must cause the user agent to fail the connection.

So it seems to include 204, but that doesn't make it clear either. 

I haven't checked if it was even implemented interoperably in between browsers.

Suggestion:

Either of those:
* Specify it in the section 5 with other HTTP codes
* Remove the sentence "a client can be told to stop reconnecting using the HTTP
204 No Content response code."

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Thursday, 6 September 2012 20:07:39 UTC