On my NGINX setup, when a url is too long, there seems to be an issue where it redirects the user back to the main page

Is there a setting in NGINX that I can alter that enables longer URLs ?

I'm thinking of this option below, but I'm not sure.

large_client_header_buffers number size

However the documentation doesn't really explain this option well.

  • How long are your URLs? You'd need to get up into the thousands of characters before you start having issues. I don't think it's having an issue with your header length, as it would be sending a 414 response instead of a redirect if that were the case. Can you provide more details about the issue that you're seeing? – Shane Madden Jan 9 '12 at 19:32
  • @ShaneMadden The lenght of the urls are a little over 100 characters. I've checked the error logs and there isn't any kind of 414 error being displayed.The links look something like this knowledgebase/article/14/what-is-the-meaning-of-owner--group--and-everyone-in-the-permissions-panel-/ – Nick M. Jan 11 '12 at 17:38

Alright guys (and girls?), After a long search I finally found out what this issue was being caused by.

There is a third party module that can be installed on php called suhosin. More information about the project can be found here http://www.hardened-php.net/suhosin/

Anyway you need to open up your php.ini and find these following 3 line. If they do not exist then you need to create them with the proper variables

suhosin.get.max_name_length (default 64)
suhosin.post.max_name_length (default 64)
suhosin.request.max_varname_length (default 64)

I hope this saves someone the trouble I had to go through to finally resolve! Enjoy!


You got it right probably. You need to up that from the defaults at large_client_header_buffers 4 4k/8k

If you are maxing out the buffer, there is a possibility nginx is just redirecting you to the index page. But the nginx manual says: if the client send a bigger header nginx returns error "Request URI too large" (414). Look in the logs to see what response you are getting. If you get the 414 then this is definitely it.

  • What would be a larger large_client_header_buffers? large_client_header_buffers 8 8k ? Does that look right to you? – Nick M. Jan 11 '12 at 17:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.