W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2006

[Bug 211] Inconsistencies about Destination header

From: <bugzilla@soe.ucsc.edu>
Date: Sat, 28 Jan 2006 07:49:52 -0800
Message-Id: <200601281549.k0SFnqmL014177@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=211

julian.reschke@greenbytes.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From julian.reschke@greenbytes.de  2006-01-28 07:49 -------
There are three issues with these changes:

1) The URL considerations (that used to live under 12. Multistatus) do not apply
to request headers (at least this was never discussed).

2) The BNF grammar productions should constrain the values to what we want (for
instance, relative references need to be absolute paths).

3) The draft still requires (MUST) a 502 response code when the server can't
access the destination. As 502 is not the proper code here (it's not a server
error), making this a MUSt level requirement simply in unacceptable.





------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
You are on the CC list for the bug, or are watching someone who is.
Received on Saturday, 28 January 2006 15:49:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:13 GMT