Re: upstream sent too big header while reading response header from upstream

2014-02-10 Thread rubenarslan
Yes, that's quite probably it! Then I guess it's on Jerome to weigh in, I don't know the exact reasoning for doing so, I would have thought it would be more appropriate to hash the request body in the cache key, but maybe that's not possibly using nginx? OpenCPU allows for request bodies up to 500

Re: upstream sent too big header while reading response header from upstream

2014-02-10 Thread rubenarslan
Hi Basti, thanks, I found the SO post myself. I had not set up the directives properly, so thought the fix didn't work. It does now. I also think they described a different problem, as in my case no cookies were sent, headers were fairly small and two requests with pretty much identical headers se

Re: upstream sent too big header while reading response header from upstream

2014-02-10 Thread rubenarslan
Hi, after some further testing I discovered that I had the order in which various nginx config files are called wrong. Because location {} isn't merged, but overridden, my directives never 'took'. Setting proxy_buffer_size 8k; kept the errors from occurring. As I wrote on Github https://github.

Re: upstream sent too big header while reading response header from upstream

2014-02-10 Thread rubenarslan
Hi Maxim & Jeroen, I'm the user Jeroen mentioned. I'm sorry for only being to produce sporadic errors earlier, I now made a test case which reliably produces the error, both on our server and Jeroen's server (so it's hopefully not just my amateur status with nginx). Of course, the ridiculously la