fix nginx append slash to respect proxy #14814
Merged
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 is already fixed in awx-operator. See https://github.com/ansible/awx-operator/blob/a534c856dbebc853191fb2547346007a60f137db/roles/installer/templates/configmaps/config.yaml.j2#L215 This just makes it so a development environment can also work correctly behind a proxy Fixes problem of GET to https://$PROXY/something/awx/v2/me rewritten to https://$AWX/something/awx/v2/me/ (which doesn't exist) instead path is correctly rewritten as https://$PROXY/something/awx/v2/me/
chrismeyersfsu
approved these changes
Jan 29, 2024
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.
SUMMARY
This is already fixed in awx-operator.
See https://github.com/ansible/awx-operator/blob/a534c856dbebc853191fb2547346007a60f137db/roles/installer/templates/configmaps/config.yaml.j2#L215 This just makes it so a development environment can also work correctly behind a proxy
Fixes problem of
GET to https://$PROXY/something/awx/v2/me
rewritten to https://$AWX/something/awx/v2/me/ (which doesn't exist)
instead path is correctly rewritten as https://$PROXY/something/awx/v2/me/
ISSUE TYPE
COMPONENT NAME
AWX VERSION