You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the output of an action in the swagger-ui there is also a line for curl with an accept header. But this accept header is always application/json regardless of which options one has choosen for the response content type.
For example in your demo the GET pet/findByStatus, choose application/xml as Response Content Type and available as status. Then the shown Curl prompt is
curl -X GET --header "Accept: application/json" "http://petstore.swagger.io/v2/pet/findByStatus?status=available"
See also
The same seems to be the case for the Request Headers if it is shown. We encountered the error first here infolis/infolis-web#21
The text was updated successfully, but these errors were encountered:
As part of the output of an action in the swagger-ui there is also a line for curl with an accept header. But this accept header is always
application/json
regardless of which options one has choosen for the response content type.For example in your demo the GET pet/findByStatus, choose application/xml as Response Content Type and available as status. Then the shown Curl prompt is
See also
The same seems to be the case for the
Request Headers
if it is shown. We encountered the error first here infolis/infolis-web#21The text was updated successfully, but these errors were encountered: