W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

[Bug 17222] New: treat status code 308 consistently with 301, 302, and 307

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 May 2012 12:25:51 +0000
To: public-webapps@w3.org
Message-ID: <bug-17222-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17222

           Summary: treat status code 308 consistently with 301, 302, and
                    307
           Product: WebAppsWG
           Version: unspecified
          Platform: All
               URL: http://www.w3.org/TR/XMLHttpRequest/#infrastructure-fo
                    r-the-send-method
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XHR
        AssignedTo: annevk@annevk.nl
        ReportedBy: julian.reschke@gmx.de
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


The spec has specific requirements for HTTP status codes 301, 302, and 307.
Status code 308 should be added here.

Approved IETF spec:
<https://datatracker.ietf.org/doc/draft-reschke-http-status-308/>

IANA registry:
<http://www.iana.org/assignments/http-status-codes/http-status-codes.xml>

Related mozilla bug: <https://bugzilla.mozilla.org/show_bug.cgi?id=758973>

-- 
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 Monday, 28 May 2012 12:25:54 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT