Handle invalid/missing Content-Length header in POST. #2
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
|
Minor fix and small improvements... |
|
Also added fix for #1 |
gwerbin
pushed a commit
to gwerbin/httpd-echo
that referenced
this pull request
Mar 26, 2021
gunchev
force-pushed
the
master
branch
2 times, most recently
from
80afec9 to
bcf7011
Compare
Signed-off-by: Doncho N. Gunchev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While testing my http(s) client in C++ using boost::beast... I forgot to add the Content-Length header in the POST method...