Document some of the properties of Early-Data #592
Merged
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
According to RFC 7231, Section 8.3.1.
|
Your proposal looks very clear to me, despite your jetlag :-) I agree with you that Vary should be OK. I don't even think we need to say anything about it then. |
MikeBishop
approved these changes
Apr 24, 2018
draft-ietf-httpbis-replay.md
Outdated
| @@ -282,6 +283,13 @@ marked with Early-Data was sent in early data on a previous hop. Requests that | |||
| contain the Early-Data field and cannot be safely processed MUST be rejected | |||
| using the 425 (Too Early) status code. | |||
|
|
|||
| The `Early-Data` header field carries a single bit of information and clients | |||
| MUST include at most one instance. However multiple instances MUST be treated | |||
There was a problem hiding this comment.
Comma after "However", or just drop the word.
mnot
approved these changes
Apr 25, 2018
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.
According to RFC 7231, Section 8.3.1.
I didn't include anything here about Vary because I wanted to discuss that first and these seemed uncontroversial. It seems OK to say that Vary is permitted here because we expressly talk about varied reactions based on the presence of Early-Data. If that's right, I will amend this with a second commit. (I'm jetlagged, so being a little cautious.)