Ensures CORS headers are configured properly in httpd proxy server. #135
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
bbranan
approved these changes
Mar 26, 2021
fozboz
pushed a commit
to scholarsportal/duracloud
that referenced
this pull request
Jul 22, 2021
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.
Ensures CORS headers are configured properly in httpd proxy server.
JIRA Ticket: https://jira.lyrasis.org/browse/DURACLOUD-1306
What does this Pull Request do?
With the last release we upgraded to the latest beanstalk environment which uses a slightly different file structure for configuring the apache proxy server. This update ensures that CORS and other httpd .conf files are being picked up by the beanstalk apache configuration process.
How should this be tested?
Build and deploy (currently deployed to dev)
curl -u username:password https://./durastore// -i
Verify the presence of CORS headers in the response.
Interested parties
Tag (@ mention) interested parties or, if unsure, @duracloud/committers