W3C home > Mailing lists > Public > www-validator-cvs@w3.org > September 2013

[Bug 23196] New: Content-Type HTTP headers lacks charset information when json format is requested

From: <bugzilla@jessica.w3.org>
Date: Tue, 10 Sep 2013 12:33:31 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-23196-169@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23196

            Bug ID: 23196
           Summary: Content-Type HTTP headers lacks charset information
                    when json format is requested
           Product: Validator (Nu)
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: General
          Assignee: mike+validator@w3.org
          Reporter: tgambet@w3.org
        QA Contact: www-validator-cvs@w3.org

When requesting a result as json the server does not specify a complete
Content-Type header:
[ Content-Type: application/json ]

Since the content is UTF-8 the header should be:
[ Content-Type: application/json; charset=utf-8 ]

----------------

$ lwp-request -e -d 
"http://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.w3.org&out=json"
Cache-Control: no-cache
Connection: close
Date: Tue, 10 Sep 2013 12:26:18 GMT
Accept-Encoding: gzip
Server: Jetty(6.1.26)
Content-Type: application/json
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Access-Control-Allow-Origin: *
Client-Date: Tue, 10 Sep 2013 12:26:17 GMT
Client-Peer: 128.30.52.91:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 10 September 2013 12:33:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:55 UTC