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

Document how to allow blocked files #712

Open
rmccue opened this issue Dec 4, 2022 · 2 comments
Open

Document how to allow blocked files #712

rmccue opened this issue Dec 4, 2022 · 2 comments
Labels
developer advocacy Developer Advocacy related tasks

Comments

@rmccue
Copy link
Member

rmccue commented Dec 4, 2022

By default, certain types of requests are blocked, but you might want to allow these through. For example, all requests for files starting with . are blocked, but /.well-known is part of several important protocols that you might want to handle.

These can be handled by adding a rule, but must be added using the regex-style match for specificity which could catch people out and can be hard to debug if you don't have the source.

eg (the ~ marks this as regex-style):

location ~ /\.well-known/webfinger {
	try_files $uri /index.php$is_args$args;
}
@roborourke
Copy link
Contributor

Should we just bake that into the main nginx config?

@rmccue
Copy link
Member Author

rmccue commented Mar 6, 2023

For .well-known? It's not that commonly used for the stuff we're doing (I was implementing ActivityPub), so I'd say only the general docs are needed.

@missjwo missjwo added the developer advocacy Developer Advocacy related tasks label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer advocacy Developer Advocacy related tasks
Projects
None yet
Development

No branches or pull requests

3 participants