Paul Prescod papresco at technologist.com
Mon Sep 21 00:56:34 BST 1998

John Cowan wrote:
> The trouble is that "http://whoever.net/foo?bar" doesn't mean the
> same thing as "http://whoever.net/foo%3Fbar"; the latter induces the
> server to look for a file named "foo?bar", whereas the former queries
> the resource "foo" with the request "bar".

That's true, I should have thought of that. Of course URLs are a
string-based language, and the language has to have reserved characters.
But what of the characters that are "unsafe because gateways and other
transport agents are known to sometimes modify such characters". I was
thinking more about those. It seems that they should be handled
transparently, as MIME encoding is in a modern mail program. Of course ~
is usually bandied about despite its "unsafeness", but I would be
surprised if browsers are smart enough to encode it during transmission
for "safety."

 Paul Prescod  - http://itrc.uwaterloo.ca/~papresco

It's such a 
Being always

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)

More information about the Xml-dev mailing list