W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

[Bug 18772] New: Should getAllResponseHeaders() end with \r\n?

From: <bugzilla@jessica.w3.org>
Date: Tue, 04 Sep 2012 18:46:07 +0000
To: public-webapps@w3.org
Message-ID: <bug-18772-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18772

           Summary: Should getAllResponseHeaders() end with \r\n?
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XHR
        AssignedTo: annevk@annevk.nl
        ReportedBy: Ms2ger@gmail.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


The spec says

> Return all the HTTP headers, excluding headers that are a case-insensitive
> match for Set-Cookie or Set-Cookie2, as a single string, with each header
> line separated by a U+000D CR U+000A LF pair, excluding the status line,
> and with each header name and header value separated by a U+003A COLON
> U+0020 SPACE pair.

That seems to suggest "no", but is that intentional?

-- 
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 Tuesday, 4 September 2012 18:46:08 GMT

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