Title: Content Security Policy Automatic Log Function
Last modified: February 24, 2018

---

# Content Security Policy Automatic Log Function

 *  Resolved [rebornhairppp](https://wordpress.org/support/users/rebornhairppp/)
 * (@rebornhairppp)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/content-security-policy-automatic-log-function/)
 * Hi Dimitar,
 * First off, thanks for a wonderful plugin. I am really enjoying all of the intuitive
   features.
 * For your next release, would there be any way in which you can design a specific
   automated option to log any content security policies that the browser warrants
   as problematic?
 * I know Dylan, the developer of the WP Content Security Policy plugin, has a separate
   CSP Log option embedded within the plugin which logs all CSP issues. So, rather
   than browsing your website and visiting each page and having to laboriously read
   and adjust my CSP headers accordingly based on the error shown in the developer
   tools console tab, this added option with a click of a button will automatically
   insert the correct syntax in the appropriate CSP category (e.g. default src, 
   font src, etc.)
 * You can see a screenshot of this option at my URL: [https://www.resurrectedhair.net/wp-content/uploads/2018/02/WP-Content-Security-Policy-Log.png](https://www.resurrectedhair.net/wp-content/uploads/2018/02/WP-Content-Security-Policy-Log.png).
 * Looking at the pic, for the img-src issue with one click of a button I can Allow
   IMG-SRC Access. Clicking on this button will automatically insert the correct
   syntax in the img-src category to allow access for – in my example – secure.gravatar.
   com
 * This extra value-added benefit will save tremendous time for us rudimentary users.
 * If you can be so kind to let me know if this feature can be added in the next
   release that would be graciously appreciated!
 * Aside from this addition, kudos to your brilliant efforts in making such a useful
   plugin!
 * All my best,
 * Joe

Viewing 1 replies (of 1 total)

 *  Plugin Author [Dimitar Ivanov](https://wordpress.org/support/users/zinoui/)
 * (@zinoui)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/content-security-policy-automatic-log-function/#post-10133200)
 * Hi [@rebornhairppp](https://wordpress.org/support/users/rebornhairppp/)
 * As one of the more complex headers for setup I think it make sense. Definitely
   worth to consider.
 * Thanks for suggestion.
 * Regards,

Viewing 1 replies (of 1 total)

The topic ‘Content Security Policy Automatic Log Function’ is closed to new replies.

 * ![](https://ps.w.org/http-headers/assets/icon-128x128.png?rev=1413576)
 * [HTTP Headers](https://wordpress.org/plugins/http-headers/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/http-headers/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/http-headers/)
 * [Active Topics](https://wordpress.org/support/plugin/http-headers/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/http-headers/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/http-headers/reviews/)

## Tags

 * [CSP](https://wordpress.org/support/topic-tag/csp/)
 * [log](https://wordpress.org/support/topic-tag/log/)

 * 1 reply
 * 2 participants
 * Last reply from: [Dimitar Ivanov](https://wordpress.org/support/users/zinoui/)
 * Last activity: [8 years, 2 months ago](https://wordpress.org/support/topic/content-security-policy-automatic-log-function/#post-10133200)
 * Status: resolved