Make default EXPECT_100_THRESHOLD 1Mb #4814
Closed
Conversation
This file contains 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
bagder
approved these changes
Jan 14, 2020
|
I mentioned this change on the mailing list, just to give people a chance to respond or have opinions before merge. Let's just keep this open a few days for that purpose. |
|
OK. Thanks! |
|
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
detailed reference: #3524
When using a wrapper library of libcurl, I had a problem in HTTP protocol because Header "Expect: 100-continue" is added implicitly.
'Expect' Header is written clearly in RFC 7231 but not so commonly used now.
As we can see #3524 discussion, this constraint can be relaxed, and it seems that has already been concluded so.