On 2/21/2015 6:33 PM, Walter Underwood wrote: > Never do POST for a read-only request. Never. That only guarantees that you > cannot reproduce the problem by looking at the logs. > > If your design requires extremely long GET requests, you may need to re-think > your design.
I agree with those sentiments ... but those who consume the services we provide tend to push the envelope well beyond any reasonable limits. My Solr install deals with some Solr queries where the GET request is pushing 20000 characters. The queries and filters constructed by the website code for some of the more powerful users are really large. I had to configure haproxy and jetty to allow HTTP headers up to 32K. I'd like to tell development that we just can't handle it, but with the way the system is currently structured, there's no other way to get the results they need. If I were to make it widely known internally that the Solr config is currently allowing POST requests up to 32 megabytes, I am really scared to find out what sort of queries development would try to do. I raised that particular configuration limit (which defaults to 2MB) for my own purposes, not for the development group. Thanks, Shawn
