Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

Support XML in- and ouput (and content negotiation) #1

Closed
kleijnweb opened this issue Sep 6, 2015 · 0 comments
Closed

Support XML in- and ouput (and content negotiation) #1

kleijnweb opened this issue Sep 6, 2015 · 0 comments

Comments

@kleijnweb
Copy link
Owner

Currently only supports JSON.

Content Negotiation

Clients not sending an Accept header will receive content in the format first listed under produces for that operation, or if not available, application/json.

If the Accept header excludes application/json and produces is not set or does not include application/json, an empty response with status code 406 is returned.

If a client sends content other than application/json and the content-type is not listed in the operation's consumes listing, an empty response with status code 406 is returned.

@kleijnweb kleijnweb changed the title Support XML in- and ouput Support XML in- and ouput (and content negotiation) Sep 6, 2015
kleijnweb pushed a commit that referenced this issue Mar 22, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant