On 03/28/12 13:47, Vladimir Kotal wrote: <snip>
clicked on second/third/... page of the results. The Referer (which contained long URL with all projects listed) made the HTTP headers too long for Tomcat which as a result returned error 400. We fixed that
I should probably add that we are not hitting the limit of the query URL length itself (which would result in HTTP error code 414), yet. If we get there then we will bump the limit (with the LimitRequestLine configuration directive in Apache which itself serves as proxy to the Tomcat in our environment. This would probably trigger the bump of the HTTP headers length limit and URL length limit in Tomcat so that both servers are in line w.r.t. URL related limits). I've seen reports of 128K long URLs to be working with Apache 2.2 so there is still some headroom left.
Anyway, from our perspective the ability to pass URLs to searches is important so going the POST way does not really work for us. Of course, passing very long URLs in emails/bug databases seems silly so there might be some alternative solutions to think of. (e.g. ability to generate short URLs or tunable which would switch the behavior from default GET to POST; not sure if it possible to set the method dynamically based on URL length)
v. _______________________________________________ opengrok-discuss mailing list opengrok-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
