http://ppewww.ph.gla.ac.uk/~flavell/www/formgetbyurl.html Not sure what
authorative basis this has, but it did turn up from NCSA based CGI
specifications of yesteryear.
Maybe the MIME specification for application/x-www-form-urlencoded
wherever that is (cant find it either).
It must be no
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
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/rf
I'm not trying to encode semi-colon into QS. I'm trying to use
semi-colon as a replacement for & or rather & when correctly encoded
into a HTML document. On the basis that it makes the documents smaller
and the code easier to write. I have been left with the impression they
are directly su
In a URL the semi-colon indicates the start of path parameters (as
opposed to the normal query parameters) as defined in rfc2616 (HTTP1.1
spec) et al.
Thus, you can't tell tomcat to use it as a query string delimiter.
JSESSIONID is a well known path parameter for Servlet 2.2+ Containers.
To use
I swear I had application code working that was using semi-colons to
delimit query string parameters. I'm sure I've also seen TC append a
";JSESSIONID=" at the end of the URL.
But my own application code written like:
String val = request.getParameters("name");
Yeilds: val="value;name2=foo
