Add cache-buster re-write rule to nginx.conf option 2 examples#224
Merged
kingjia90 merged 1 commit intopimcore:2024.4from Feb 11, 2025
Merged
Conversation
This properly re-routes cache-buster routes to a custom controller when using the "Option 2" nginx example to block access to the protected folder but still allow Portal Engine/etc. users to authenticate and access via custom controller.
ghost assigned 
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 subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
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 properly re-routes cache-buster routes to a custom controller when using the "Option 2" nginx example to block access to the protected folder but still allow Portal Engine/etc. users to authenticate and access via custom controller.
See pimcore/pimcore#18074 in the pimcore/pimcore repo.