devcontainer: fix Authorization header not passed to PHP via Apache#60737
Open
Jay-1409 wants to merge 4 commits into
Open
devcontainer: fix Authorization header not passed to PHP via Apache#60737Jay-1409 wants to merge 4 commits into
Jay-1409 wants to merge 4 commits into
Conversation
Signed-off-by: Jay shah <166749819+Jay-1409@users.noreply.github.com>
This file contains hidden or 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.
Summary
This PR improves the devcontainer setup by fixing an issue where Apache was not forwarding the Authorization header to PHP, which could break authentication flows inside the container.
It adds an Apache configuration during devcontainer setup that ensures the Authorization header is correctly passed through to PHP using SetEnvIfNoCase. The config is automatically enabled via a2enconf.
This resolves authentication issues in the Docker/devcontainer environment where tokens or auth headers were previously being stripped, ensuring consistent login and API behavior during local development.
3. to review, feature component)stable32)AI (if applicable)