Cloudflare and their new SSL for free users

@Xon, that made no sense to me at all. I'm not very technical. Could you try to explain it so that a newbie like me understands it?
You must validate who is sending the "real ip" header. If it is Cloudflare or a http aware loadbalancer, Great!

If it's a spammer saying they are coming from <you server ip here>, and you accept that; not so great.
 
FYI @eva2000 replied with this:

The Nginx http to https redirect is same as mentioned at Nginx HTTPS / SSL Google SPDY configuration

Code (Text):
server {
server_name domain.com www.domain.com;
return 301 https://$server_name$request_uri;
}
 
Why use CF-Connecting-IP? It does not make sense. Not to mention that they always change the IP addresses...
:confused:

The CF-Connecting-IP header is how CloudFlare passes in the original IP before they proxy the connection. The list of IP addresses is who is allowed to send it, and it's up to the website owner to keep that list up-to-date (but it hasn't changed for a while).
 
Top Bottom