Send HTTP status code 431 if request header is too large #126
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clue
changed the title
Member
Author
|
Rebased now that #125 is in |
jsor
approved these changes
Feb 19, 2017
WyriHaximus
approved these changes
Feb 20, 2017
Member
WyriHaximus
left a comment
WyriHaximus
left a comment
There was a problem hiding this comment.
Looks good but could you fix merge conflicts?
Member
Author
|
Rebased now that #127 is in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, sending an invalid request results in the same error message as sending a valid request that is too large:
HTTP/1.1 400 Bad Request.This simple PR change it so that the latter will now use the more descriptive error message:
HTTP/1.1 431 Request Header Fields Too LargeBuilds on top of #124