Details
-
Bug
-
Resolution: Done
-
Major
-
8.0.0.CR1
-
None
Description
Problem:
HTTP Domain Management Interfaces returns invalid Content-Type header:
Content-Type: application/json;utf-8
This breaks management for lots of REST clients.
Proposed solution:
According to W3C and rfc2616 the Content-Type header should be:
Content-Type: application/json; charset=utf-8
BTW: JBoss 7.1.1 behaviour is ok. It does not send any charset parameter at all.
Example:
Request contains the following headers:
3 > Accept: application/json 3 > Content-Type: application/json ...
Wildfly 8.0.0.CR1 response after digest authentication is:
4 < 200
4 < Authentication-Info: nextnonce="EB9WbpMrUuwNMTM4NzY3MDc2NzAxMgXaHXwaKEWPxbxUj1ihuOg="
4 < Connection: keep-alive
4 < Content-Type: application/json;utf-8
4 < Transfer-Encoding: chunked
JBoss 7.1.1 response after digest authentication is:
4 < 200 4 < Content-type: application/json 4 < Date: Sat, 21 Dec 2013 23:48:36 GMT 4 < Transfer-encoding: chunked