• Resolved pr3d

    (@pr3d)


    Content-Security-Policy HTTP header: Bad content security policy: Expecting uri-reference but found "https://$".

    • This topic was modified 4 years, 7 months ago by pr3d.
Viewing 1 replies (of 1 total)
  • Plugin Author Andrea Ferro

    (@unicorn03)

    Hello pr3d thank you for reporting the error “Content-Security-Policy HTTP header: Bad content security policy: Expecting uri-reference but found "https://$".

    We are finishing the new update that implements an HTTP Content-Security-Policy (CSP, report-uri directive instructs the user agent to report attempts to violate the content security policy. These violation reports consist of JSON documents sent via an HTTP POST request to the specified URI, now this feature is available with version 2.0.6 of Headers Security Advanced & HSTS WP.

    Warning: although the report-to directive is intended to replace the deprecated report-uri directive , report-to is not yet supported in most browsers. So, for compatibility with current browsers, we have also added both report-uri and report-to compatibility (thus making Headers Security Advanced & HSTS WP already compatible and working).

    Example:
    Content-Security-Policy: report-uri /csp-violation-endpoint-report-headers-security-advanced/; report-to default

    ** We welcome any additional feedback you may have so that we can provide you with optimal support.

    Thank you again for using Headers Security Advanced & HSTS WP and if possible please leave a review.

    • This reply was modified 4 years, 7 months ago by Andrea Ferro.
    • This reply was modified 4 years, 7 months ago by Andrea Ferro.
Viewing 1 replies (of 1 total)

The topic ‘error when checking on html validator’ is closed to new replies.