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

[Bug 224] add example for URI escaping in DAV:href

From: <bugzilla@soe.ucsc.edu>
Date: Sun, 22 Jan 2006 08:35:55 -0800
Message-Id: <200601221635.k0MGZtdg028998@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org


julian.reschke@greenbytes.de changed:

           What    |Removed                     |Added
OtherBugsDependingO|                            |46
              nThis|                            |
         AssignedTo|joe-bugzilla@cursive.net    |elias@cse.ucsc.edu

------- Additional Comments From julian.reschke@greenbytes.de  2006-01-22 08:35 -------
See proposed change below (and

Section 12., para. 9:

    If a server allows resource names to include characters that aren't
    legal in HTTP URL paths, these characters must be percent-encoded on
    the wire (see [RFC3986], section 2.1).  For example, it is illegal to
    use a space character or double-quote in a URI.  URIs appearing in
    PROPFIND or PROPPATCH XML bodies (or other XML marshalling defined in
    this specification) are still subject to all URI rules, including
    forbidden characters.


 12.2.1  Example for correct URL handling
    Consider the collection http://example.com/sample/ with the internal
    member URL http://example.com/sample/a%20test and the PROPFIND
    request below:
      PROPFIND /sample/ HTTP/1.1
      Host: example.com
      Depth: 1
    In this case, the server should return 'href' elements containing
    o  'http://example.com/sample/' and
       'http://example.com/sample/a%20test', or
    o  '/example.com/sample/' and '/example.com/sample/a%20test'.
    Note that even though the server may be storing the member resource
    internally as 'a test', it must be percent-encoded when used inside a
    URI reference (see [RFC3986], Section 2.1).  Also note that a legal
    URI may still contain characters that need to be escaped within XML
    character data, such as the ampersand character.

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Sunday, 22 January 2006 16:35:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:35 UTC