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

Support for Content-Security-Policy: upgrade-insecure-requests; #57

Open
2 tasks done
dariolongo opened this issue Mar 18, 2022 · 1 comment
Open
2 tasks done

Comments

@dariolongo
Copy link

dariolongo commented Mar 18, 2022

🌱 Feature Request

Is your feature request related to a problem? Please describe.

A clear and concise description of what you want and what your use case is.

Hi,
There is a way to set the upgrade-insecure-requests in the CSP headers?

Describe the solution you'd like

A clear and concise description of what you want to happen.

A new parameter like "upgradeInsecureRequest" of type bool (default false)

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Documentation, Adoption, Migration Strategy

If you can, explain how users will be able to use this and how it might be documented. Maybe a mock-up?

Additional context

Add any other context or screenshots about the feature request here.


  • I've tried to find similar issues and pull requests
  • I would like to work on this feature 💪🏻
@sitch
Copy link

sitch commented Nov 13, 2023

bump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants