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
Content Negotiation - Offered and Accepted #75
Comments
jeevatkm
changed the title
Provide a way to limit request content-type and request body size
Config Options to limit request content-type and request body size
Jul 8, 2017
jeevatkm
changed the title
Config Options to limit request content-type and request body size
Content Negotiation and Request Body Size Limit
Jul 26, 2017
jeevatkm
changed the title
Content Negotiation and Request Body Size Limit
Content Negotiation - Offered and Accepted
Jul 26, 2017
Closed
Also known as |
jeevatkm
added a commit
that referenced
this issue
Aug 5, 2017
jeevatkm
added a commit
that referenced
this issue
Aug 6, 2017
Merged
jeevatkm
added a commit
to go-aah/tools
that referenced
this issue
Aug 6, 2017
jeevatkm
added a commit
that referenced
this issue
Aug 7, 2017
Merged :) |
jeevatkm
added a commit
to go-aah/docs
that referenced
this issue
Aug 8, 2017
jeevatkm
added a commit
to go-aah/app-templates
that referenced
this issue
Jul 4, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Content Negotiation
Content negotiation is used to validate what is being
offered
andaccepted
by server in-terms of request and response. (also known asContent-Type
restriction)Offered -
Accept
HTTP header RFC2616For example: Client sends
Accept
header asapplication/xml
. However server only supports serving JSON i.e.application/json
. Then server responds with406 Not Acceptable
.Accepted -
Content-Type
HTTP header RFC2616For example: Client sends
Content-Type
header asapplication/xml
. However server only supports JSON payload as request body. Then server responds with415 Unsupported Media Type
.Configuration
The text was updated successfully, but these errors were encountered: