grok.JSON should set correct response headers

Bug #362902 reported by Martijn Faassen on 2009-04-17
4
Affects Status Importance Assigned to Milestone
grok
Medium
Unassigned

Bug Description

Grok's JSON support currently responds with text/plain, but should be responding with text/json as the Content-Type instead.

Changed in grok:
importance: Undecided → Medium
milestone: none → 1.0
Michael Haubenwallner (d2m) wrote :
Changed in grok:
status: New → Fix Committed
Changed in grok:
status: Fix Committed → Fix Released
Florent (florent.x) wrote :

Actually, the IANA approved mimetype is 'application/json'.
http://www.ietf.org/rfc/rfc4627.txt

Changed in grok:
status: Fix Released → New
Florent (florent.x) wrote :
Changed in grok:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers