[ https://issues.apache.org/jira/browse/SOLR-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587533#comment-14587533 ]
Ramkumar Aiyengar commented on SOLR-7681: ----------------------------------------- Is there any situation in which GETs are preferable? This might be a simple matter of adjusting defaults to use POST. Currently SolrJ defaults to GET.. > HttpSolrClient fails with a confusing error when a GET request is too big > ------------------------------------------------------------------------- > > Key: SOLR-7681 > URL: https://issues.apache.org/jira/browse/SOLR-7681 > Project: Solr > Issue Type: Bug > Reporter: Ramkumar Aiyengar > Priority: Minor > > If a request is sent with too long an URL for GET, the Solr server responds > as follows: > {code} > HTTP/1.1 413 FULL head > Content-Length: 0 > Connection: close > Server: Jetty(8.1.10.v20130312) > {code} > {{oascsi.HttpSolrServer.executeMethod}} currently in such a situation, goes > ahead and tries to parse a {{Content-Type}} header in such a case and ends up > with a {{SolrServerException: Error executing query}} caused by > {{org.apache.http.ParseException: Invalid content type}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org