Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

And is it configurable? Can I set up Tomcat so that a URL with, say, 200K of query params goes through successfully to the contained servlet?

Yes, I know one should use POST when you have lots of data; that's a less pleasant option in this particular case. The contained application (a search engine) expects a GET request to perform a search.

share|improve this question

3 Answers 3

up vote 41 down vote accepted

You can edit tomcat/conf/server.xml's HTTP/1.1 Connector entry, and add a maxHttpHeaderSize="65536" to increase from the default maximum of 8K or so, to 64K. I imagine that you could up this number as high as necessary, but 64K suffices for my needs at the moment so I haven't tried it.

<Connector port="8080" maxHttpHeaderSize="65536" protocol="HTTP/1.1" ... />
share|improve this answer
Very useful, solved my problem with Solr. Seems we were scratching on the default 8192 limit in the server.xml config, without noticing, and suddenly hit it. Painful gotcha: nothing nowhere was logged about that, the connections were silently dropped (I don't recall the HTTP Status anymore). I stumbled over the documentation at before, however I didn't associate the maxHttpHeaderSize by its name nor its description to be related to the GET request query parameters itself too. – mark Mar 16 '10 at 11:49
We also just hit the same limit in Solr, nothing but a blank white page... :( The maxHttpHeaderSize did the trick. – user85116 Sep 27 '12 at 15:37
Same here :) Very useful tip, thank you. – steve Dec 21 '12 at 11:11
I think the maxHttpHeaderSize="100000" is not possible, it should be in multiply by 1024. I have changed the maxHttpHeaderSize="1048576" which is 1024*1024 and it is still not working. – user152949 Jan 11 '13 at 7:40
An accepted answer, "maxHttpHeaderSize="65536" does not work It worked before because of bug in Tomcat. URL/URI has nothing to do with HTTP Headers. – Fuad Efendi Sep 11 at 18:08

The length of an HTTP GET request is not enforced by RFC2616, as Microsoft reports for its IE max length support page.

So, the maximum GET length is a client (browser) related issue. If your app is used by people you can force to use a given browser then you can simply find what is the length this browser support.

In every case I suggest a look to the Wikypedia page about those browser related issues on the Query string (the part of the request bringing parameters for server side apps, the one following the "?" eventually present in a request.

Of course maybe tomcat will put a limit too, on the server side. RFC says:

Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).

so you can easily test if Tomcat has a limit and find out what this limit is simply using different requests starting with a very long one giving the error and going down by one half. Then use bisection method to fast find the exact value.

share|improve this answer
Albert, I was aware that Tomcat had a limit out of the box (something like 8K); I wondered if there were a limit that even configuration could not overcome. – Michael Gundlach Aug 24 '09 at 17:14

You can change the config at Tamcat server ( ..\Tomcat 6.0\conf\server.xml )

< Connector port="8983" maxHttpHeaderSize="100000" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />

Hope it will help you...

share|improve this answer

Your Answer


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.