Update fork from main repo #2
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
Collapse TLS errors down to two.
... as 'details' can be used. Also, note availability of details where appropriate.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
Fix: #1215. HTTP/1.1 messaging is not normative anymore.
digest-headers: Fix typos, add changelog.
Remove references to "validator fields"
* consistent use of quote * New algorithms are lowercase. More consistent editorial rules.
We forgot to align this part with the SHA-1 deprecation.
Always use digest-algorithm (with dash). See #1211.
Align missing digest-algorithm parts. See #1211
…o two types (#1167) * Fill out TODOs in PRIORITY_UPDATE, split H3 frames into two types * Allow PRIORITY_UPDATE as initial signal * Reserved the selected experimental frame type values in the temporary IANA registry at https://github.com/quicwg/base-drafts/wiki/Temporary-IANA-Registry. * Incorporate a bunch of suggestions from Roy and others Co-authored-by: ianswett <ianswett@users.noreply.github.com> Co-authored-by: Martin Thomson <martin.thomson@gmail.com> Co-authored-by: Kazuho Oku <kazuhooku@gmail.com> Co-authored-by: Mike Bishop <mbishop@evequefou.be>
The old text had a loose definition of when to apply buffered frames. It also had a fair amount of repetition. This change tweaks the sections a bit so that we have one that discusses how a server should handle PRIORITY_UPDATES for either initial signal or reprioritization. It incorporates the suggestions on issue #1260 mixed in with some text we already had. I leaves the question of resolving stream limit definition to #1261. Co-authored-by: Kazuho Oku <kazuhooku@gmail.com>
Co-authored-by: Mark Nottingham <mnot@mnot.net>
…minated Allow connection_terminated to be emitted for mid-stream errors.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
Fix markdown.
clean up editorial notes and issues list
Defines "same-site" with respect to SameSite cookies, for user-interface-element-triggered reload navigations. Explicitly defines and clarifies behavior for all other reload requests.
Fix: #1190. Remove algorithm specific rules for content identifiers.
* Consider redirects when defining same-site * Reference HTML instead of FETCH. Align with HTML language * Add a date to HTML reference * Revert "Add a date to HTML reference" This reverts commit 301edde. * Add permanent anchor reference for same site algorithm * Specifically address both a missing client and a null client * Add to changelog
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.
No description provided.