]
Stuart Douglas reassigned WFLY-2681:
------------------------------------
Assignee: Stuart Douglas (was: Brian Stansberry)
HTTP Management Interface Content-Type header is broken
-------------------------------------------------------
Key: WFLY-2681
URL:
https://issues.jboss.org/browse/WFLY-2681
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Domain Management
Affects Versions: 8.0.0.CR1
Reporter: Dino Tsoumakis
Assignee: Stuart Douglas
Fix For: 8.0.0.Final
*Problem:*
HTTP Domain Management Interfaces returns invalid Content-Type header:
{code}
Content-Type: application/json;utf-8
{code}
This breaks management for lots of REST clients.
*Proposed solution:*
According to [
W3C|https://www.w3.org/International/O-HTTP-charset] and
[
rfc2616|http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7] the Content-Type
header should be:
{code}
Content-Type: application/json; charset=utf-8
{code}
BTW: JBoss 7.1.1 behaviour is ok. It does not send any charset parameter at all.
*Example:*
Request contains the following headers:
{code}
3 > Accept: application/json
3 > Content-Type: application/json
...
{code}
Wildfly 8.0.0.CR1 response after digest authentication is:
{code}
4 < 200
4 < Authentication-Info:
nextnonce="EB9WbpMrUuwNMTM4NzY3MDc2NzAxMgXaHXwaKEWPxbxUj1ihuOg="
4 < Connection: keep-alive
4 < Content-Type: application/json;utf-8
4 < Transfer-Encoding: chunked
{code}
JBoss 7.1.1 response after digest authentication is:
{code}
4 < 200
4 < Content-type: application/json
4 < Date: Sat, 21 Dec 2013 23:48:36 GMT
4 < Transfer-encoding: chunked
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: