Feature/force-upstream-to-use-http-1-1 #128
Open
Conversation
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
added 3 commits
July 29, 2021 15:41
|
@rpardini, hi. Is it possible to merge this? We are currently facing the same issue with a 426 Upgrade Required error, with cr.yandex as the upstream. |
ChandonPierre
added a commit
to coreweave/docker-registry-proxy
that referenced
this pull request
Jan 30, 2024
from rpardini#128 nginx does not support http2 as a client; this alleviates registries that return 426 when using http2
ChandonPierre
added a commit
to coreweave/docker-registry-proxy
that referenced
this pull request
Jan 31, 2024
from rpardini#128 nginx does not support http2 as a client; this alleviates registries that return 426 when using http2
rpardini
added
the
outdated
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.
Ties to #102
Added ENV check and include file to force upstream to use http 1.1
Use case - we have a harbor upstream registry sits behind an envoy proxy that requires connections to use http2.
This PR forces the connection to use http 1.1
Please ignore whitespace differences :)