[
https://issues.apache.org/jira/browse/SOLR-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated SOLR-5517:
-----------------------------
Attachment: SOLR-5517.patch
{quote}
In my opinion, we should for this case not fallback to something like the crazy
RAW parser (I agree, this is wrong and leads to confusion). Instead we should
return a better HTTP status like:
415 Unsupported Media Type
{quote}
I like this idea. I only want to make sure the example [~rcmuir] gave does not
result in a confusing 200 with empty results.
Here is a new patch returning 415 for a post missing content type.
> Treat POST with no Content-Type as application/x-www-form-urlencoded
> --------------------------------------------------------------------
>
> Key: SOLR-5517
> URL: https://issues.apache.org/jira/browse/SOLR-5517
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan Ernst
> Attachments: SOLR-5517.patch, SOLR-5517.patch
>
>
> While the http spec states requests without a content-type should be treated
> as application/octet-stream, the html spec says instead that post requests
> without a content-type should be treated as a form
> (http://www.w3.org/MarkUp/html-spec/html-spec_8.html#SEC8.2.1). It would be
> nice to allow large search requests from html forms, and not have to rely on
> the browser to set the content type (since the spec says it doesn't have to).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
