[SOLR-15116] Wrong HTTP status for HEAD request

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 8.7, 8.8, 8.9, 8.10, 8.11
• Fix Version/s: 8.11.2, 9.1
• Component/s: Schema and Analysis
• Labels: ManagedStopwordFilterFactory ManagedSynonymFilterFactory REST Solr
• Assignee: Eric Pugh
• Reporter: Thomas Corthals
• Created: 28/Jan/21 16:02
• Updated: 27/Oct/22 02:52
• Resolved: 12/Feb/22 17:21

Description

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.

$ 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

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:

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.

Issue Links

• is caused by: SOLR-14659 Remove restlet from Solr
• is related to: SOLR-16274 HEAD request for managed resource returns 500 Server Error
• links to: GitHub Pull Request #495