max size of GET query in search is reached. replace with POST fixes about solr-php-client HOT 3 CLOSED

sorry for the slow reply.

Yes, there are some reasons to use GET for searches rather than defaulting to a 
POST operation. The primary 
reason is that POST operations aren't cacheable by a reverse proxy. Solr is now 
capable of outputting 
configurable Cache-Control / Expires headers for responses. A system 
administrator can take advantage of 
this by setting up a reverse proxy between Solr clients and the service to 
cache these responses with the 
intention of removing load on Solr Service itself. 

However, it makes sense to allow the user to choose. The SolrJ implementation 
added a way of specifying the 
method that should be used during a query, I'll do the same for my search 
method.

available as of r7

Issue 52 has been merged into this issue.