: This feels like a bug, is it ticketed? Solr::Request::Select requests : are POSTing URL encoded name/value pairs so the Content-type is : appropriate...But Solr::Request::AddDocument (and others) are posting : xml so the Content-type should be text/xml. There needs to be logic : for differentiating between the two.
At the moment, when POSTing xml docs to /update the SolrUpdateServlet ignores the content-type -- but it would definitely be wise to fix this in solrb since the recently commited alternate way of doing updates (which allows for plugable UpdateRequestHandlers so we can start supporting alternate formats for updates) requires that the content-type be set appropriately: application/x-www-form-urlencoded for simple key=val pairs, multipart/* for file upload style updates, and anything else for "raw posting" of data. -Hoss
