docs: clarify limitation around reverse_proxy #457
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
The previous documentation was clear on handling http->https proxying, but not the other way round. They did not cover the case of proxying to a unix socket, either. There are special considerations when proxying to caddy in either of these cases, that should be mentioned.
dbaynard
force-pushed
the
push-ynpwtuyomzuk
branch
from
9aed03f to
1e0cd2e
Compare
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.
Simple change, would have saved me multiple hours of work.
I assume Reverse_proxy with custom http payload - Help - Caddy Community still holds.
Edit: I've added a further, related commit. Again, hours of work.