HTTP ERROR: 400, missing content stream about solr-php-client HOT 6 CLOSED

Issue 56 has been merged into this issue.

Reiterating comment from issue 56

This problem existed on PHP version >= 5.2.6 and < 5.2.10.  In those versions 
there was a problem where the http context options were not treated as 
documented when curl wrappers were enabled in the compile.

See the comment here: http://www.php.net/manual/en/context.curl.php#85551 

In svn trunk (see svn checkout page:  
http://code.google.com/p/solr-php-client/source/checkout), the code now lets 
you assign a transport implementation to use - it defaults to an HTTP url 
wrapper implementation, but a straight cURL based implementation is provided as 
well. Another alternative would be to implement your own transport.

i was using php 5.3.3 when I saw the issue notes in issue 56

Lukas,

Hopefully, it wasn't a regression in PHP. The issues seemed so similar I made 
the logical assumption they were related, sorry if that is not the case.  

Are you still seeing this problem? And if so, can you confirm or deny whether 
changing the code to use an array for the header context option corrected it 
like we see in 5.2.6.  

My best current suggestion is still to switch to the newest code and try using 
one of the Curl based transports:

// the Curl transport creates and reuses a single cURL session handle
// depending on your PHP version may leak memory over a large number of requests
$transportInstance = new Apache_Solr_HttpTransport_Curl();

// the CurlNoReuse transport creates and releases a cURL session handle for 
each request
$transportInstance = new Apache_Solr_HttpTransport_CurlNoReuse();

// a transport instance can either be given to the constructor
$solr = new Apache_Solr_Service(..., $transportInstance);

// or, it can be set at any time
$solr->setHttpTransport($transportInstance);

i have switched off curl wrappers. its experimental anyway. i dont have 
anything but 5.3.3 compiled atm. i will point the author of sfSolrPlugin to 
consider one of the above transports.

Using a different http transport, substituting your own, or changing php 
configuration are all workable for this situation. This isn't an issue for the 
majority, so i'm going to mark it won't fix.