On 2/21/2015 1:46 AM, steve wrote: > Careful with the GETs! There is a real, hard limit on the length of a GET url > (in the low hundreds of characters). That's why a POST is so much better for > complex queries; the limit is in the hundreds of MegaBytes.
The limit on a GET command (including the GET itself and the protocol specifier (usually HTTP/1.1) is normally 8K, or 8192 bytes. That's the default value in Jetty, at least. A question for the experts: Would it be a good idea to force a POST request in SolrEntityProcessor? It may be dealing with parameters that have been sent via POST and may exceed the header size limit. Thanks, Shawn
