Is this [1] the correct archive to use? By mangled, I mean, the full request wasn't making it to my server, only partial data, which caused it to fail.
Thanks for the advice, Jordan [1] http://haproxy.1wt.eu/download/1.5/src/snapshot/haproxy-ss-LATEST.tar.gz On Sun, Mar 2, 2014 at 5:27 AM, Lukas Tribus <luky...@hotmail.com> wrote: > Hi Jordan, > > > > I'm running into an issue with one of our API endpoints that takes in a > > fairly large amount of data over a PUT (or sometimes POST) request body. > > This would cause the server to timeout, and after some investigation it > > looked like the request was being mangled. We switched from SSL to > non-SSL > > for api requests (not ideal) to make it work, but then determined if we > > lowered our batch sizes it seemed to fix the issue. We can't always > control > > the size of the incoming data however. > > > > I'm wondering, is there a value I can adjust to increase the ability to > > handle larger requests over SSL? > > > > > > Using: haproxy 1.5-dev21 - Ubuntu 13.10 > > Not sure what exact timeout or issue you are hitting. I would suggest to > upgrade to current code [1] to benefit from the recent bugfixes. Quite some > fixes are related to SSL since dev21. > > If it still doesn't work, enable logging (httplog) and check for errors. > > You said the data was mangled, can you elaborate? > > > > Regards, > > Lukas > > > [1] http://haproxy.1wt.eu/download/1.5/src/snapshot/ >
