Please make the new protocol rewrite explicitly https, not protocol relative.
1. http://www.paulirish.com/2010/the-protocol-relative-url/
2. protocol relative is invalid for Google AMP, as it should be
3. protocol relative breaks things in weird ways (ad/tracking redirects)
Can’t agree more with @jb510 . You can make it default to relative, but give us an option to change it to https only. Please!!
Hi Guys,
Sorry for the confusion – what you’re describing is how protocol rewrite works now. Let me clarify:
In version 1.x we had code IN the plugin that rewrote https:// and http:// to //.
In version 3.x of the plugin we allow you to toggle the Automatic HTTPS Rewrites setting on CloudFlare.com. This setting will only rewrite http urls we know can be loaded over https.
Finally, we settled upon doing something smart: upgrade a URI from http:// to https:// if we know that the resource can be served using HTTPS. To figure out which links are upgradable we turned to the EFF’s excellent HTTPS Everywhere extension and Google Chrome HSTS preload list to augment our knowledge of CloudFlare sites that have SSL enabled.
We are very grateful that the EFF graciously accepted to help us with this project.
The HTTPS Everywhere ruleset goes far beyond just switching http:// to https://: it contains rules (and exclusions) that allow it (and us) to target very specific URIs.
We continued calling the feature “Protocol Rewrite” in our WordPress plugin to try to avoid confusion with our less technical users but we actually no longer rewrite to relative URLs.
Thanks,
John
@jwineman Alright man, thank you. Also, you guys are really doing a great job providing all of us with so many features for free. Keep it up.
