Aye. It just states for that, amongst others, amphersand and semi-colon
are reserved characters within the query string.
This got me looking coz I assumed that the structure of the http get
query string was defined somewhere in rfc rather than just a convention.
I found a few resources saying it was recommended to support ";" as a
delimiter;
http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2
But I also found the likely candidate in TC that does the parsing of the
query string:
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/Parameters.java?rev=1.15&view=markup
Just for my peace of mind does anyone know where the "standard" use of
amphersand to delimit name-value pairs in a http get query string is
defined?
Jon
Darryl L. Miles wrote:
http://www.faqs.org/rfcs/rfc2396.html section 3.3 seems to be the best
reference so far.
This RFC only specifies correct URI syntax, it does not mandate how that
URI is used under any scheme (like "http:") is to be used.
Darryl L. Miles wrote:
The reference you cite http://www.faqs.org/rfcs/rfc2616.html (el al)
maybe you could also cite the section I should look at. A simple
search for "param" or "semi" yeilds no related results. I have spent
an hour looking into the issue over the weekend and found the
specification that covers the URI scheme for "http:" from this angle
it seems to leave the part after the ? to denote the start of a query
string vague. Which lead me to a presumption that it was HTTP server
dependant on its interpretation, since for example the CGI.pm modules
changed over from & to ; as the standard param delimiter with
generated URLs, providing the resulting URL talks back to itself (the
CGI.pm module) all will be well in the world but if it links to a TC
server then there would appear to be a problem.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
