This repository has been archived by the owner on Jun 23, 2022. It is now read-only.
feat(http): support parsing content-type of HTTP request #593
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.
rDSN
http_server
currently ignores entirely the HTTP body, headers, except for URL query-params. Therefore, only URL could be used for the HTTP-client to send arguments.In order to support serving HTTP post-form ("application/x-www-form-urlencoded") requests, our HTTP server must be able to parse "Content-Type" field in the HTTP header.
So in this PR, I add support to parse "Content-Type" in rdsn
http_message_parser
. The result will be insidemsg->buffers[3]
.