[
https://issues.apache.org/jira/browse/AMBARI-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Halterman updated AMBARI-12482:
----------------------------------------
Description:
Ambari-server returns JSON, yet specifying an Accept header such as Accept:
application/json yields a 406:
{
"status": 406,
"message": "Not Acceptable"
}
There should be no problem specifying application/json since that's what Ambari
provides by default. Ideally, application/xml should be supported as well since
JAX-RS can use resource serializers such as Jackson to take care of this
automatically.
This is significant for REST API clients/libs that require an Accept header.
was:
Ambari-server returns JSON, yet specifying an Accept header such as Accept:
application/json yields a 406:
{
"status": 406,
"message": "Not Acceptable"
}
There should be no problem specifying application/json since that's what Ambari
provides by default. Ideally, application/xml should be supported as well since
JAX-RS can use resource serializers such as Jackson to take care of this
automatically.
This is significant for REST API clients that require an Accept header.
> ambari-server's API should support Accept header
> ------------------------------------------------
>
> Key: AMBARI-12482
> URL: https://issues.apache.org/jira/browse/AMBARI-12482
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Jonathan Halterman
> Priority: Minor
>
> Ambari-server returns JSON, yet specifying an Accept header such as Accept:
> application/json yields a 406:
> {
"status": 406,
"message": "Not Acceptable"
}
> There should be no problem specifying application/json since that's what
> Ambari provides by default. Ideally, application/xml should be supported as
> well since JAX-RS can use resource serializers such as Jackson to take care
> of this automatically.
> This is significant for REST API clients/libs that require an Accept header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
