[WIP] Add HTTP/3 columns#204
Open
LPardue wants to merge 1 commit into
Open
Conversation
ghedo
suggested changes
Jan 7, 2020
| <td class="ok">yes</td> | ||
| <td class="ok">yes</td> | ||
| <td class="ok"><a href="https://blog.cloudflare.com/introducing-http2/">yes</a></td> | ||
| <td class="ok"><a href="https://blog.cloudflare.com/http3-the-past-present-and-future/">no</a></td> |
There was a problem hiding this comment.
Suggested change
| <td class="ok"><a href="https://blog.cloudflare.com/http3-the-past-present-and-future/">no</a></td> | |
| <td class="ok"><a href="https://blog.cloudflare.com/http3-the-past-present-and-future/">yes</a></td> |
:)
Author
There was a problem hiding this comment.
I put no because we don't support the yet-to-be-published RFC version of HTTP/3. However, the class should be alert not ok, which I just fixed up.
Add an HTTP/3 column to server and CDN/PaaS tables. In the interest of simplicity, this column reflects support for the final RFC version of HTTP/3. Since the IETF are yet to publish this version, all entries begin with the value of "no". Over time, we'll populate cells and amend this commit. Sensible thresholds might include HTTP/3 support merged into server mainline codebase (or module equivalents) and CDN/PaaS betas that have public announcements.
Owner
|
👍 Thinking out loud: we could note the QUIC version supported by some platforms but set level to alert, to indicate that this is a transitionary state. WDYT? |
Author
|
Apologies for dropping the ball on this one. 2 years on, since RFC 9000 is published now and most implementations are moving to support HTTP/3 with QUIC v1, I think we can now just focus on that. I'll make some fixups to this PR and will prompt for another review. |
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
3 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.
Fixes #203.
Add an HTTP/3 column to server and CDN/PaaS tables.
In the interest of simplicity, this column reflects
support for the final RFC version of HTTP/3. Since
the IETF are yet to publish this version, all entries
begin with the value of "no".
Over time, we'll populate cells and amend this commit.
Sensible thresholds might include HTTP/3 support merged
into server mainline codebase (or module equivalents)
and CDN/PaaS betas that have public announcements.