According to Geoff Hutchison:
> On Fri, 16 Apr 1999, Gilles Detillieux wrote:
> > That doesn't mean we shouldn't fix Display::createURL() in 3.1.2. The way
> ...
> > So, I'd see a change here as a bug fix. Thoughts?
>
> I suspect it's a relatively easy fix, so I say we go for it. But if it
> looks like we're going to be doing much URL encoding/decoding (beyond the
> URLTrans.cc code), we should hold off until we can do a nice cleanup of
> that code. As you said, it's better to get 3.1.2 out.
Sounds good to me. By the way, right now createURL() is the only place
where encodeURL() is called, so I think this will have minimal impact.
I'd like to make encodeURL's default list of valid punctuation characters
consistent with what is normally allowed (unencoded) in CGI.
I tried entering the following string as the search word in a search.html
form that uses the GET method, in Netscape Communicator 4.04:
~!@#$%^&*()_+`-=[]{}\|;:'",<.>/?
This is what appeared in the words= part of the query string:
%7E%21@%23%24%25%5E%26*%28%29_%2B%60-%3D%5B%5D%7B%7D%5C%7C%3B%3A%27%22%2C%3C.%3E%2F%3F
So it seems the only unencoded punctuation characters, from Netscape, are
@*_-. while the current default for encodeURL is ?_@.=&/:
Lynx seems to give the same results. Unless someone points me to a
standard reference that contradicts this, I'm tempted to go with what
Lynx & Netscape use for encoding.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
