I agree; it should return an error instead of mislead/confuse the user. ~ David
Jack Krupansky-2 wrote > I don’t get any error or any effect from this curl command: > > curl http://localhost:8983/solr/update?commit=true --data-binary ' > <delete> > <query> > sku:td-01 > </query> > </delete> > ' > > But, if I add the xml header, it works fine: > > curl http://localhost:8983/solr/update?commit=true -H "Content-Type: > application/xml" --data-binary ' > <delete> > <query> > sku:td-01 > </query> > </delete> > ' > > It would be nice if Solr would default to application/xml, but a friendly > error return would be better than a no-op in this case. > > FWIW, curl –v shows this header being sent if I don’t specify it > explicitly: > > Content-Type: application/x-www-form-urlencoded > > -- Jack Krupansky ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Bug-Improvement-No-op-and-no-error-for-Solr-update-if-no-application-xml-header-tp4027800p4027877.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
