[SOLR-5272] Schema REST API not returning correct Content-Type for JSON

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Information Provided
• Affects Version/s: 4.4
• Component/s: Response Writers
• Assignee: Unassigned
• Reporter: David Arthur
• Created: 25/Sep/13 17:34
• Updated: 11/Jan/18 16:07
• Resolved: 11/Jan/18 16:07

Description

The new Schema REST API is not returning application/json as the Content-Type when wt=json (or when wt is omitted).

Examples:

$ curl -s -D - http://localhost:8888/solr/collection1/schema/fields -o /dev/null

HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Date: Wed, 25 Sep 2013 17:29:24 GMT
Accept-Ranges: bytes
Transfer-Encoding: chunked

$ curl -s -D - http://localhost:8888/solr/collection1/schema/fields?wt=json -o /dev/null

HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Date: Wed, 25 Sep 2013 17:30:59 GMT
Accept-Ranges: bytes
Transfer-Encoding: chunked

$ curl -s -D - http://localhost:8888/solr/collection1/schema/fields?wt=xml -o /dev/null

HTTP/1.1 200 OK
Content-Type: application/xml; charset=UTF-8
Date: Wed, 25 Sep 2013 17:31:13 GMT
Accept-Ranges: bytes
Transfer-Encoding: chunked

$ curl -s -D - http://localhost:8888/solr/collection1/schema/fields?wt=javabin -o /dev/null

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Date: Wed, 25 Sep 2013 17:31:45 GMT
Accept-Ranges: bytes
Transfer-Encoding: chunked

This might be more than just a schema REST API problem - perhaps something to do with the Restlet/Solr writer bridge? I peeked in the code but saw nothing obvious.