The HTML 4 spec requires a "name=value" pair between the &'s, by my reading. Not necessarily in every URL, but at least when a form is submitted via a GET request. ref. http://www.w3.org/TR/html4/interact/forms.html#h-17.13.3.4 That's the commonest way to create URL query strings but not the *only* way, so I think it's appropriate to log a warning but not an error for non-compliant URLs. -- Len
On Fri, Feb 29, 2008 at 1:43 PM, Mark Thomas <[EMAIL PROTECTED]> wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
