jivany

Ah, so it turns out that Railgun is what was breaking the ability of this plugin to return the original IPs. Since disabling Railgun everything is working fine.

So…

Any chance you can make this plugin work with Railgun enabled on CloudFlare’s partner webhosts?

Hehe. I guess that is a reasonable answer. If it’s not really for general consumption, maybe the button should be buried somewhere instead of at the top of the CDN config page?

Come on, you put out a new version and you can’t take 2 seconds to shorten the name?

Thanks!

Yeah, I ended up doing that but I’m trying to understand why it’s broken now and it wasn’t before.

Sorry, I need to get my test server up and running again. I’ll provide more info once I’ve done that.

Sorry, I haven’t had a chance to debug this further. Once I get my test server up and running again I’ll provide more info.

This is definitely a timing issue. Any WP user profile links in the template suggest the user is still logged in but the meta widget shows the user is not logged in.

Is there anything to be concerned about with the large number of errors coming from the same IPs?

I spent a couple minutes looking at this and realized that the private_filter function isn’t quote correct. It fails to return anything as any good filter function should.

Here is the end of the function currently (around line 314):

} else {
		//user not logged in, do nothing, let normal 404 handling continue
	}
}

It needs to be updated as shown below:

} else {
		//user not logged in, do nothing, let normal 404 handling continue
		return $type;
	}
}

I haven’t looked at the other scenarios before this one where there is nothing returned but in my quick tests it appears everything works so far.

Jeff