[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Unwrapping urn:public:...
/ dcpleland@ftnetwork.com was heard to say: | Tony Coates wrote: | | >We aren't reinventing anything. I certainly saw "+" in URLs long before I saw | >"%20". It just happens that Netscape people tend to use the "+" form and IE | >users tend to use "%20" (or just a plain space). | | Having never seen '+' as a white space in a url, used in my decade | of markup experience, I cannot vouch for your experience. And | having used Netscape for all of that time, I am bewildered by your | assertin that netscape people used it. Tony is absolutely right about using '+' to represent a space, at least in HTTP URLs, although I wasn't thinking about that. What's interesting is that there appears to be no spec that explicitly defines this behavior. The HTML 3.2 Recommendation says (in the discussion of the ISINDEX tag): Note that space characters are mapped to "+" characters and that normal URL character escaping mechanisms apply. For further details see the HTTP specification. But I don't see any reference to this form of escaping in either RFC 1945 (HTTP/1.0) or RFC 2616 (HTTP/1.1) or any of the URL RFCs. Be seeing you, norm -- Norman.Walsh@Sun.COM | DNA neither cares nor knows. DNA just is. And XML Standards Engineer | we dance to its music.--Richard Dawkins Technology Dev. Group | Sun Microsystems, Inc. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC