Nginx Content Security Policy Example Syntax For Normal Websites

We discussed about  Content Security Policy before –  Content Security Policy for adding report-uri. Readers are complaining that many sites are proving snippets which are throwing odd errors in Nginx, like nginx: [emerg] invalid number of arguments in “add_header”, nginx: [emerg] invalid parameter “self”, nginx: [emerg] unexpected “s”. So, Here is Nginx Content Security Policy Example Syntax For Normal Websites Which Will Not Throw Any Error.

 

Before Implementing Nginx Content Security Policy Example

 

You Can Use With Nginx Content Security Policy Example on Normal Website Only the Report Only Function. Honestly, you can not use Content Security Policy with Google AdSense or any Third Party Ads. It is an impractical idea to add header to prevent XSS attack. With so many browsers and devices, except loading webpage from 1 -2 sources it is just not possible. We are giving example of both.

 

Nginx Content Security Policy Example

 

Those websites providing wrong syntax for Nginx. This is a common way to add any header on Nginx :

The above will give this output upon curl -I header checking :

In that way, this is a perfect clean Nginx Content Security Policy Example :

You will get all resources on :

… just register and use the tool. Suppose the web software suggested this :

You can make it to this for nginx:

It will avoid this error :

However, with the above some browsers may not allow anything expect text to load. We have tested may ways to only use Nginx Content Security Policy for protecting for XSS on websites with Third Party Ads running, has CDN. It is just not possible. Safari will load webpage without CSS, Images. Even this (notice default-src * unsafe-inline unsafe-eval) :

…forces not to load any Google Ads on Safari.

 

Nginx Content Security Policy Report Only Example (This is What You Can Use)

 

We are using this :

If you run :

You will get :

The above is safe for your website as webmaster to apply on whole website. Except reporting it has no action. That method of reporting is not exactly easy though.

 

Use Content Security Policy Dynamically, Not One Rule For Whole Website

 

Checkout pages, payment pages needs more security. You can inject the restricted header on the must be under microscope webpages. WordPress /wp-login.php is one such webpage, if you have PHPMyAdmin, that is important to filter. You can use PHP to pass the header.

Tagged With nginx content-security-policy , content security polict nginx , Content-Security-Policy-Report-Only nginx , nginx content security policy best way , nginx add_header content-security-policy frame-ancestors , nginx add header content-security policy frame-ancesters , https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1835 oH9IJTRwLmWnwbMESyDo2ftWJAuk5s_PSRyQnmzcfmFGzgwCtetkGzU7PwjDterr 9103a4d3891f6a1a9dba2d78a4141560feab13f8&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme , https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1831 qjKmgFZWeNahZ_oLTuO80XsSKiUOm7vm7wgXSQFU3pE_safil_PNcrpLu15UKrmf 8bbe99c8cbf34aaec66a24ffc7bb6cd8f4d90615&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme , https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1826 XfnuOHCDkh9XVhAYJLilY1F_5g95G9vN7ZpMmMVpYJa5y2HHp57joQEtDkx2mVO6 b100c4cca353da21bcb801221d604fb24351fa57&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme , Content Security Policy report-uri webforms