[
https://issues.apache.org/jira/browse/SOLR-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836018#comment-13836018
]
Uwe Schindler commented on SOLR-5517:
-------------------------------------
I checked the rawrequest parser: It adds the query string to the content. I
think the bigger problem why the whole request posted by Robert did not work is
the fact that by using the raw request parser, the /select handler cannot
handle that. The raw request parser is only useful for update request handlers.
On the other hand: if you send some crazy non-null content type to something
else than the update request handlers, they may produce the same strange
results (maybe if you have a typo in the "application/x-formdata-foo-bar"
stuff). The /select request handler should (in my opinion) check some request
properties and throw an error if they don't fit the actual request.
> Return HTTP error on POST requests with no Content-Type
> -------------------------------------------------------
>
> 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]
