We regularly get individual REST GET requests significantly over that length;
the only tuning parameter we've done in that regard is:
tune.bufsize 128000
I don't actually recall if this was mandatory to address the issue, but I'm
thinking that it was.
-Richard
Richard Stanford
CTO | KIMBIA
512-474-4447 x777
On Sep 10, 2012, at 12:24 PM, Lange, Kevin M. (GSFC-423.0)[RAYTHEON COMPANY]
wrote:
> Hi,
> Our public-facing service provides a REST api to search for products
> (geospatial science data), which requires in many cases very long URLs to
> craft the search. We seem to be hitting a limit of around 8K before we
> receive a 400 Bad request from lighttpd. We're trying to determine if
> lighttpd is causing this, or haproxy. We have a dev/test stack
> (lighttpd/haproxy on Linux) and an OPS stack of the same. Our OPS stack we
> thought we had test results of the URL length maximum, but after we upgraded
> haproxy to the latest on our OPS stack, we noticed that people began
> complaining about the URL length issue (maximum 8k). Is there a configurable
> item in haproxy which would limit a URL length to ~8k? Suggestions from
> searches show that tune.bufsize might control this. We'd like to offer our
> customers a 10k length for REST api calls.
> - Kevin
>
> Kevin Lange
> [email protected]
> [email protected]
> W: +1 (301) 851-8450
> Raytheon | NASA | ECS Evolution Development Program
> https://www.echo.nasa.gov | https://www.raytheon.com
>
