[
https://issues.apache.org/jira/browse/SOLR-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589032#comment-14589032
]
Ramkumar Aiyengar commented on SOLR-7681:
-----------------------------------------
Actually thinking through this further, with 5x Jetty is an implementation
detail, so we *know* the GET size limit, forget about figuring out or storing
in clusterstate. The simplest solution might be to just always switch to POST
if that limit is reached, and we don't break compatibility since it wouldn't
have worked before. For the power user, we can always provide a way to tweak
the GET to POST cutoff limit.
> 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: [email protected]
For additional commands, e-mail: [email protected]
