We use a dual host model where Server A is a proxy_pass for Server B
which
runs our PHP code. Both servers use the same nginx.conf and
large_client_header_buffers 4 32k; option.
414 error no matter what changes are made. Any ideas?
On Fri, Apr 12, 2013 at 06:54:26PM +0800, Scott E. MacKenzie wrote:
We use a dual host model where Server A is a proxy_pass for Server B which
runs our PHP code. Both servers use the same nginx.conf and
large_client_header_buffers 4 32k; option.
414 error no matter what changes are made. Any ideas?
Make sure to adjust the directive in a default server as well if
there are more than one virtual host configured for the listen
socket in question.
We are performing a rather large data update via our api using GET and
have
hit this error. The changes to both nginx.conf and to the vhosts make
no
difference and the process dies with 414 at the same line of the update.
After some more resarch we came across a post on browser URL limits. Do
you
think that we are hitting the maximum limit for GET and that is the
reason
why the adjustments are not making any difference?
On Fri, Apr 12, 2013 at 10:34:07PM +0800, Scott E. MacKenzie wrote:
Hi Maxim,
The logs (even with debug enabled) do not produce any evidence to isolate
this to the browser hitting a maximum count. However, on the other hand
there is no evidence of large_client_header_buffers being reached either.
Any other thought on isolating the issue beyond changing the GET to POST?
First of all you should check if request actually hits nginx, it
should be as easy as looking into access log for 414.
Yes, did that before posting to the list and no error 414 is logged. I
have not come across this before and hence the question to the list.
Based
on the lack of anything logged it does look to be a hard limit being
reached in the browser, but again, I thought that I would post to the
list
to ensure that we have not overlooked anything.
The logs (even with debug enabled) do not produce any evidence to
isolate
this to the browser hitting a maximum count. However, on the other hand
there is no evidence of large_client_header_buffers being reached
either.
Any other thought on isolating the issue beyond changing the GET to
POST?
On Fri, Apr 12, 2013 at 11:15:13PM +0800, Scott E. MacKenzie wrote:
Hi Maxim,
Yes, did that before posting to the list and no error 414 is logged. I
have not come across this before and hence the question to the list. Based
on the lack of anything logged it does look to be a hard limit being
reached in the browser, but again, I thought that I would post to the list
to ensure that we have not overlooked anything.
If you are unsure, you can always look at what happens on the wire
with tcpdump/wireshark/whatever.