Clarify HTTP header value encoding and decoding requirements (#793) #816
Whoa there!
You have triggered an abuse detection mechanism.
Please wait a few minutes before you try again;
in some cases this may take up to an hour.
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
…ents#793) * fix: Clarify HTTP header value encoding and decoding requirements Fixes cloudevents#777 Once this is agreed, we should also document conformance tests, but it's unclear at the moment where they should live. Signed-off-by: Jon Skeet <jonskeet@google.com>
|
Note: this is #793, but against the |
|
approved on 4/22 |
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.
Fixes #777
Once this is agreed, we should also document conformance tests, but
it's unclear at the moment where they should live.
Signed-off-by: Jon Skeet jonskeet@google.com