Add apache TLS reverse proxy configuration #329
+158
−0
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
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.
Description
A template for Apache host reverse proxy configuration was added. A short tutorial was also written in the docs folder.
I've spent too much time configuring overleaf with apache, so here comes the PR.
Feel free to suggest modifications on both the configuration and the tutorial, the configuration is derived from the NGINX reverse proxy configuration and works on my side (including websockets forwarding and secure cookie) but I may have missed things.
Related issues / Pull Requests
Issue #78 seems to be a misconfiguration of websockets forwarding through apache.
Contributor Agreement