Use HTTP Semantics for accept option
#267
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
msporny
requested review from
ChristopherA,
danpape,
dmitrizagidulin,
mccown and
peacekeeper
as code owners
TallTed
approved these changes
Jan 9, 2026
wip-abramson
approved these changes
Jan 12, 2026
peacekeeper
approved these changes
Jan 15, 2026
dmitrizagidulin
approved these changes
Jan 22, 2026
Collaborator
dmitrizagidulin
left a comment
dmitrizagidulin
left a comment
There was a problem hiding this comment.
👍 looks good, just needs resolving rebase conflict.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
This PR is an attempt to address issue #116 by modelling the value of the
acceptoption according to RFC9110 (HTTP Semantics).Preview | Diff