Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 1 down vote favorite

Title says it all: from which version onward is the LimitRequestFieldSize no longer hardcoded to a max. of 8k?

It seems 2.2.15 is still affected.

share|improve this question
Buddy, forgive me for mentioning this, but you have been a member of SF for well over a year. In this time, you have asked several questions, but accepted the answer for none. Local etiquette is that after a reasonable time, you accept the best answer for any given question, and that helps drive SF's reputation system. You don't have to do this, but as a result we see a big red warning "0% accept rate" by your username. That warning may discourage some people from answering your questions. If you had time to go through your old questions and accept an answer for each, that would be good. – MadHatter Jan 14 at 15:00
You are right, of course. I usually do this on StackOverflow, but often forget this for ServerFault, because i don't use it that often. Thanks for the hint! – Buddy Casino Jan 14 at 15:47

1 Answer

up vote 0 down vote

Ok, so it turns out that it works in 2.2, but you need to increase the max AJP packet size if you have a Tomcat behind it and use mod_proxy_ajp, or else it will still give a 400 Bad Request.

Specifically, set this in Apache:

LimitRequestFieldSize 65536
ProxyIOBufferSize 65536

and this in Tomcat server.xml on the ajp connector:

packetSize="65536"

Only setting LimitRequestFieldSize won't do the trick!

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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