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
Support for custom Permissions Policy HTTP header in Nginx #201
Comments
Since we are using a unique Nginx server blocks directory For example like:
|
I was going back on forth on this but I don't think So I'm proceeding with calling this After a few Google searches it looks like Roots Trellis uses a similar folder name Ref: https://roots.io/trellis/docs/nginx-includes/ Still pending integration with SlickStack installer scripts and the main Nginx config file... |
See here:
For better security/control perhaps we can include specific child includes only as they become approved by the community instead of just a wildcard include... https://github.com/littlebizzy/slickstack/blob/master/modules/nginx/nginx-conf.txt |
https://forum.nginx.org/read.php?11,256135
Not sure if still relevant. |
New default Permissions Policy submodule called https://github.com/littlebizzy/slickstack/blob/master/modules/nginx/includes/perms-policy-conf.txt You can now customize this in SlickStack. Simply edit your own file under Ref: https://github.com/littlebizzy/slickstack/blob/master/bash/ss-install-nginx-config.txt |
This is an issue we knew would eventually need to be discussed, and here it is being requested:
https://slickstack.io/forum/topic/feature-policy-header-blocking-camera-request
It gets to a bigger issue which is better support for "sub-config" files added under e.g.
/etc/nginx/conf.d/
however, the official Nginx.com docs suggest feature-specific files which doesn't really apply to SlickStack since it's mostly just http... their docs suggest child config files for e.g. http, events, stream, etc.Ref: https://docs.nginx.com/nginx/admin-guide/basic-functionality/managing-configuration-files/
I think we need to be even narrower than that for SlickStack. For example maybe
featurepolicy.conf
to focus specifically on that HTTP header, since other HTTP headers will likely remain hardcoded in SlickStack...The text was updated successfully, but these errors were encountered: