Cantaloupe reverse proxy using IP #2
Closed
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
This was referenced Aug 17, 2023
|
This has been replicated in #8 with more of the custom IA internals required, so closing this PR as 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.
This adds the reverse proxy to Cantaloupe based on using the IP address of the IA load balancer and passing the target domain explicitly as a header.
Pro: Doesn't require resolving the address of the LB/Cantaloupe server on every request -> less unnecessary traffic
Con: Hard codes IP address of the Load Balancer, so will stop working if that changes
NB: Only one of this or #3 should be merged, followed by #4 to update the address used in manifest generation