[
https://issues.redhat.com/browse/WFWIP-290?page=com.atlassian.jira.plugin...
]
Fabio Burzigotti updated WFWIP-290:
-----------------------------------
Steps to Reproduce:
The issue can be reproduced following the steps:
* execute Wildfly instance build from feature branch
* provide a deployment to register `openapi` endpoint
* send HTTP GET request to `openapi` defining the Accept header, e.g.:
{code}
curl --location --request GET 'http://127.0.0.1:8080/openapi' \
--header 'Accept: application/json-patch+json'
{code}
* the response "Content-Type" header is set to "application/json".
Used feature branch is:
https://github.com/pferraro/wildfly/tree/WFLY-12313
was:
The issue can be reproduced following the steps:
* execute Wildfly instance build from feature branch
* provide a deployment to register `openapi` endpoint
* send HTTP GET request to `openapi` defining the Accept header, e.g.:
`curl --location --request GET 'http://127.0.0.1:8080/openapi' \
--header 'Accept: application/json-patch+json'`
* the response "Content-Type" header is set to "application/json".
Used feature branch is:
https://github.com/pferraro/wildfly/tree/WFLY-12313
Response Content-Type is 'application/json' even when HTTP
request defines 'application/json-patch+json' "Accept" header
------------------------------------------------------------------------------------------------------------------------
Key: WFWIP-290
URL:
https://issues.redhat.com/browse/WFWIP-290
Project: WildFly WIP
Issue Type: Bug
Components: MP OpenAPI
Reporter: Fabio Burzigotti
Assignee: Paul Ferraro
Priority: Major
When sending HTTP request header "Accept: application/json-patch+json",
"Content-Type: application/json" response is returned.
This behavior seems to be less strict compared to what is defined by the spec, as it
states "application/json" is specifically needed in order to get the same value
back from server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)