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

About new security header: Feature Policy #134

Open
zoze opened this issue Sep 4, 2018 · 4 comments
Open

About new security header: Feature Policy #134

zoze opened this issue Sep 4, 2018 · 4 comments

Comments

@zoze
Copy link

@zoze zoze commented Sep 4, 2018

Are you support new security header: Feature Policy ?
Feature Policy

@luhis

This comment has been minimized.

Copy link

@luhis luhis commented Apr 6, 2019

i want this too. I am making a start on it here: https://github.com/luhis/NWebsec/ but there is quite a lot to do

@NF997

This comment has been minimized.

Copy link

@NF997 NF997 commented Oct 13, 2019

Awesome @luhis - would love to see a PR!

@luhis

This comment has been minimized.

Copy link

@luhis luhis commented Oct 13, 2019

@NF997 I ended up abandoning the work. NWebsec works well, but it just overs too many uses, ASP.net, ASP.net Core, code config, xml config. It just felt like a lot of the work I was doing was never going to be used by anyone.

I have started moving my own stuff over to the default header configurer in ASP.net Core

@cgountanis

This comment has been minimized.

Copy link

@cgountanis cgountanis commented Jan 15, 2020

@NF997 I ended up abandoning the work. NWebsec works well, but it just overs too many uses, ASP.net, ASP.net Core, code config, xml config. It just felt like a lot of the work I was doing was never going to be used by anyone.

I have started moving my own stuff over to the default header configurer in ASP.net Core

Do you have any good Core 3 examples of this with full configurations, etc... NWebSec has so many other options not just CSP, can you do all of them that way?

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.