[
https://issues.apache.org/jira/browse/SOLR-15116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273852#comment-17273852
]
David Eric Pugh commented on SOLR-15116:
----------------------------------------
Makes sense to me. I suspect you hit one of those corner cases that isn't
well tested in Solr. Love to see a patch.
> Wrong HTTP status for HEAD request
> ----------------------------------
>
> Key: SOLR-15116
> URL: https://issues.apache.org/jira/browse/SOLR-15116
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
> Affects Versions: 8.7
> Reporter: Thomas Corthals
> Priority: Major
> Labels: ManagedStopwordFilterFactory,
> ManagedSynonymFilterFactory, REST, Solr
>
> A GET request for a word that doesn't exist in a managed resource (stopwords
> or synonyms) returns "404 Not Found", but the HEAD request for the same child
> resource returns "200 OK" as if the word actually exists.
> {code:sh}
> $ curl -i
> "http://localhost:8983/solr/techproducts/schema/analysis/synonyms/english/foobar";
> | head -n 1
> HTTP/1.1 404 Not Found
> $ curl -I
> "http://localhost:8983/solr/techproducts/schema/analysis/synonyms/english/foobar";
> | head -n 1
> HTTP/1.1 200 OK
> {code}
> Solr 8.6.3 returns "404 Not Found" for both GET and HEAD requests for a
> non-existing child resource. This is how it SHOULD be according to [RFC
> 2616|https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4]:
> {quote}The metainformation contained in the HTTP headers in response to a
> HEAD request SHOULD be identical to the information sent in response to a GET
> request.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
