Title: CloudFlare Compatibility
Last modified: August 21, 2016

---

# CloudFlare Compatibility

 *  Resolved [Dominic](https://wordpress.org/support/users/dominicp/)
 * (@dominicp)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/cloudflare-compatibility-1/)
 * I’ve seen some indications that this plugin is compatible with CloudFlare from
   my Googling but nothing definitive. I noticed that in the `brute_get_ip` function
   you’re checking the `HTTP_X_FORWARDED_FOR` header, but there are some instances
   where that can include multiple IPs when working with CloudFlare (see [CloudFlare docs](https://support.cloudflare.com/hc/en-us/articles/200170986-How-does-CloudFlare-handle-HTTP-headers)).
 * Maybe there should be a conditional that checks for the `CF-Connecting-IP` header
   as well? Anyway, thanks for a great plugin.
 * [https://wordpress.org/plugins/bruteprotect/](https://wordpress.org/plugins/bruteprotect/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Contributor [Sam Hotchkiss](https://wordpress.org/support/users/samhotchkiss/)
 * (@samhotchkiss)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/cloudflare-compatibility-1/#post-4586447)
 * Hi Dominic– thanks for the feedback! We’ve added CF-Connecting-IP to the headers
   we look for in the latest version of BruteProtect
 *  Thread Starter [Dominic](https://wordpress.org/support/users/dominicp/)
 * (@dominicp)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/cloudflare-compatibility-1/#post-4586456)
 * Hi Sam, thanks for incorporating that header check. I took a look at the latest
   source, and I think there might be a small formatting error.
 * In the PHP `$_SERVER` variable, the `CF-Connecting-IP` header is presented as`
   $_SERVER["HTTP_CF_CONNECTING_IP"]`. So the `array_key_exists` check won’t find
   it. See this [SO answer](http://stackoverflow.com/a/14985633/931860).
 * Sorry, I should have made that more clear in my original post.
 *  Plugin Contributor [Sam Hotchkiss](https://wordpress.org/support/users/samhotchkiss/)
 * (@samhotchkiss)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/cloudflare-compatibility-1/#post-4586457)
 * Thanks, Dominic, that’s what I get for throwing things in at the last second 
   🙂 I’ve made the fix, and it’ll be in our 1.1.5 release which should be out by
   the end of next week

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘CloudFlare Compatibility’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/bruteprotect_372a22.svg)
 * [BruteProtect](https://wordpress.org/plugins/bruteprotect/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/bruteprotect/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/bruteprotect/)
 * [Active Topics](https://wordpress.org/support/plugin/bruteprotect/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bruteprotect/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bruteprotect/reviews/)

## Tags

 * [headers](https://wordpress.org/support/topic-tag/headers/)

 * 3 replies
 * 2 participants
 * Last reply from: [Sam Hotchkiss](https://wordpress.org/support/users/samhotchkiss/)
 * Last activity: [12 years, 3 months ago](https://wordpress.org/support/topic/cloudflare-compatibility-1/#post-4586457)
 * Status: resolved