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, 11 Feb 2006 01:01:36 -0800
Message-Id: <200602110901.k1B91axt009607@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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





------- Additional Comments From julian.reschke@greenbytes.de  2006-02-11 01:01 -------
Well, I guess that should be an indicator for the fact that the "does it require
implementation changes" may not be the best rule.

The whole point of allowing paths instead of URLs is to allow clients to do
something they couldn't do before. Yes, the *required* change is in the server.
But if we don't tell client implementors that they can now take advantage of it,
what was the whole point in the change?



------- 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, 11 February 2006 09:01:43 GMT

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