Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protected Web Paths: Help protect customers from accidentally adding public file folders #9452

Open
ccharlton opened this issue Feb 18, 2025 · 0 comments · May be fixed by #9457
Open

Protected Web Paths: Help protect customers from accidentally adding public file folders #9452

ccharlton opened this issue Feb 18, 2025 · 0 comments · May be fixed by #9457
Assignees
Labels
Source: Pantheor Contribution from within Pantheon, unspecified team Type: Quick Fix Issues that should be resolvable in a small PR

Comments

@ccharlton
Copy link
Contributor

https://docs.pantheon.io/pantheon-yml#protected-web-paths

Could we please add some phrasing or an additional Consideration to discourage users from adding common public files folder paths to a site's protected web paths since that breaks site functionality like asset loading, asset derivative generation? (e.g. wp-content for WP, and /sites/default/files for Drupal sites)

@ccharlton ccharlton added Source: Pantheor Contribution from within Pantheon, unspecified team Type: Quick Fix Issues that should be resolvable in a small PR labels Feb 18, 2025
@rachelwhitton rachelwhitton self-assigned this Feb 24, 2025
@rachelwhitton rachelwhitton linked a pull request Feb 24, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Pantheor Contribution from within Pantheon, unspecified team Type: Quick Fix Issues that should be resolvable in a small PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants