We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
render-link.html
Use shortcode instead
Originally posted by mhite January 20, 2025 Me again, still working through the upgrade process of .5 -> 1.0.
I used the following index.headers in my .5 site:
/* Strict-Transport-Security: max-age=31536000; includeSubDomains; preload X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Content-Security-Policy: default-src 'self'; frame-ancestors https://jamstackthemes.dev; manifest-src 'self' https://*.netlify.app; connect-src 'self' https://*.netlify.app; font-src 'self' https://*.netlify.app; frame-src mailto: https://*.paddle.com https://player.vimeo.com https://www.youtube.com; img-src 'self' https://*.netlify.app https://cdn.paddle.com data:; script-src 'self' https://cdn.paddle.com 'sha256-iIdAg2NbKitkvSjYOm5mMTqCmPgoNlTKrO9kL1KtZ7Y=' https://*.netlify.app 'sha512-RBYr6Ld4w1yVqaACrgrBLQfPgGhj/1jyacA74WxJ1KM6KVcSWymwrdDwb3HDcdpwiNJ5yssot1He0U9vXoQVlg=='; style-src 'self' https://*.netlify.app https://cdn.paddle.com 'unsafe-inline' X-Frame-Options: SAMEORIGIN Referrer-Policy: strict-origin Feature-Policy: geolocation 'self' Cache-Control: public, max-age=31536000 Access-Control-Allow-Origin: *
I am wondering if this file is still respected/used in 1.0.
The text was updated successfully, but these errors were encountered:
h-enk
No branches or pull requests
Use shortcode instead
Resources
Discussed in #1322
Originally posted by mhite January 20, 2025
Me again, still working through the upgrade process of .5 -> 1.0.
I used the following index.headers in my .5 site:
I am wondering if this file is still respected/used in 1.0.
The text was updated successfully, but these errors were encountered: