Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accept header #100

Open
r1mar opened this issue Sep 7, 2022 · 0 comments
Open

Accept header #100

r1mar opened this issue Sep 7, 2022 · 0 comments

Comments

@r1mar
Copy link
Contributor

r1mar commented Sep 7, 2022

Hello Zack,

a feature, that not implemented too.

http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358864
8.2.1 Header Accept
As defined in [RFC7231], the client MAY specify the set of accepted formats with the Accept Header.

Services MUST reject formats that specify unknown or unsupported format parameters.

If a media type specified in the Accept header includes a charset format parameter and the request also contains an Accept-Charset header, then the Accept-Charset header MUST be used.

If the media type specified in the Accept header does not include a charset format parameter, then the Content-Type header of the response MUST NOT contain a charset format parameter.

The service SHOULD NOT add any format parameters to the Content-Type parameter not specified in the Accept header.

If the Accept header is specified on an individual request within a batch, then it specifies the acceptable formats for that individual request. Requests within a batch that don’t include the Accept header inherit the acceptable formats of the overall batch request.

Regards,
Richard

r1mar added a commit to r1mar/node-odata that referenced this issue Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant