docs: add optional HTTP/3 (QUIC) configuration guide for Nginx#767
Open
zerox80 wants to merge 1 commit intoopencloud-eu:mainfrom
Open
docs: add optional HTTP/3 (QUIC) configuration guide for Nginx#767zerox80 wants to merge 1 commit intoopencloud-eu:mainfrom
zerox80 wants to merge 1 commit intoopencloud-eu:mainfrom
Conversation
5 tasks
751bfe9 to
58f7d6d
Compare
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
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.
Hey everyone,
I thought it would be a good idea to add an HTTP/3 section to the external proxy guide for users who want to get the best possible performance out of their setup.
Since HTTP/3 runs over QUIC (UDP), it brings some massive benefits for a file sync solution like OpenCloud. Things like 0-RTT handshakes, no head-of-line blocking during large uploads, and connection migration for mobile clients really make a difference in everyday use. It also prevents MITM attacks via Deep Packet Inspection since the transport layer is fully encrypted
Here is a quick breakdown of what I added:
upstreamblocks and amapdirective to keep the websocket handling clean.The HTTP/3 configurations are totally independent of the standard HTTP/2 ones, so it shouldn't confuse users who just want a basic setup.
Let me know if you want anything changed!