Hi Mark,
I know that RFC 3986 is the successor from RFC 1738, but the query
parameter definition (3.4 Page 23) isn't usefull.
The HttpUtils.parseQueryString() definition is good, but not a
complete BNF. The wikipedia
definition http://en.wikipedia.org/wiki/Query_string is much better.
OK, I also think that double "&&" is an uncorrect query part, but at
my case, some site grabber's use those
query strings to made trouble :-(
Peter
Am 29.02.2008 um 19:43 schrieb Mark Thomas:
Peter Rossbach wrote:
Hi,
I see the following warning with following request "http://
localhost:8080/snoopy/snoopy.jsp?hello=xxx&&world=yyy"
Tomct 5.5.26
==
29.02.2008 13:49:29 org.apache.tomcat.util.http.Parameters
processParameters
WARNUNG: Parameters: Invalid chunk ignored.
===
Both parameter hello and world has the correct values, but every
request logs a warning. At high
traffic sites this anno user fault made admins really unhappy.
At RFC 1738 only the following BNF are reference:
That RFC is out of date. You want RFC 3986.
Neither RFC actually defines how a parameter string should be
formatted. I did quite a bit of googling but the best reference I
found was the JavaDoc in the servlet spec for
HttpUtils.parseQueryString() which suggests your URL above does
indeed have a suspect query string because of the double &&.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
