feat: add HTTP headers and request data model - #11
Merged
Merged
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
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.
Summary
Adds the first public HTTP data-model types required by request serialization and response parsing.
Added
include/cpp_request/headers.hppcontains()/get()get()returns the first matching valueset()replaces all matching fields with one valuesrc/headers.cppset()input handlinginclude/cpp_request/request.hppMethodenum: GET, HEAD, POST, PUT, PATCH, DELETEstd::string_viewHeaderstests/headers_test.cppset()replacement semanticstests/request_test.cppOwnership model
Requestintentionally does not copy URL or body data. Those remain borrowed for the synchronous v1 execution model.Headersowns inserted names and values so callers may safely pass temporary/source strings without retaining their storage.Scope
This PR intentionally does not serialize HTTP/1.1 bytes, validate outgoing header syntax, parse responses, or execute requests through
Client. The next HTTP-layer PR can build the request serializer directly on these types.