Title: HTTPS protocol rewritting NOT for canonical URLs
Last modified: August 22, 2016

---

# HTTPS protocol rewritting NOT for canonical URLs

 *  Resolved [Jens Tonnier](https://wordpress.org/support/users/tonnier/)
 * (@tonnier)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/)
 * I love your new function of HTTPS protocol rewritting. But please don’t rewrite
   Canonical URLs (as generated from Plugins like Yoast SEO) as they absolutely 
   need the right protocol!
 * [https://wordpress.org/plugins/cloudflare/](https://wordpress.org/plugins/cloudflare/)

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

 *  [simon-says](https://wordpress.org/support/users/simon-says/)
 * (@simon-says)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679242)
 * Hi Jens,
 * Thanks so much for your feedback – to confirm, you’re talking about these type
   of tags:
 * `<link rel="canonical" href="http://example.com" />`
 * Is that correct?
 * Simon
 *  Thread Starter [Jens Tonnier](https://wordpress.org/support/users/tonnier/)
 * (@tonnier)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679265)
 * Hi Simon,
 * absolutely yes 🙂
    The so called Canonical Tag needs an absolute path, including
   the protocol. It’s one of the most important Tags for SEO.
 * Jens
 *  [simon-says](https://wordpress.org/support/users/simon-says/)
 * (@simon-says)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679286)
 * Hi Jens,
 * Yep – implemented plenty of these in my time! Just wanted to check the SEO world
   hadn’t moved onto something else I wasn’t aware of.
 * We’ll take a look at this and see what we can do for you.
 * Simon
 *  [Ben Konyn](https://wordpress.org/support/users/bkonyn/)
 * (@bkonyn)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679296)
 * The latest release broke my site!
 * I have a shortcode that generates the output
    `<form action="https://secure.worldpay.
   com/wcc/purchase" name="BuyForm" method="POST" id="worldpay">`
 * The plugin stripped the https: and so customers could no longer pay for anything!
 * How would i prevent this so i can re-enable the plugin?
 *  [simon-says](https://wordpress.org/support/users/simon-says/)
 * (@simon-says)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679297)
 * Hi Bkoyn,
 * You can turn the protocol rewriting off at any time:
 * [https://support.cloudflare.com/hc/en-us/articles/203652674-What-is-Protocol-Rewriting-in-the-CloudFlare-Wordpress-Plugin](https://support.cloudflare.com/hc/en-us/articles/203652674-What-is-Protocol-Rewriting-in-the-CloudFlare-Wordpress-Plugin)
 * If you can raise a support ticket and ask for it to be sent to me with an example
   we can take a look for you.
 * Simon
 *  [Ben Konyn](https://wordpress.org/support/users/bkonyn/)
 * (@bkonyn)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679311)
 * Thanks Simon!
 * I turned it off and all is well now.
    I’ll try to create a ticket.
 * The problem is that my site is not HTTPS but the link to eh payment site must
   be HTTPS so the protocol is not the same.
 * Thanks again
 *  [simon-says](https://wordpress.org/support/users/simon-says/)
 * (@simon-says)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679354)
 * Hi Bkoyn,
 * OK – please do send us a ticket with an example page so we can look at a fix 
   for you here.
 * Simon
 *  [dfritsch](https://wordpress.org/support/users/dfritsch/)
 * (@dfritsch)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679385)
 * We just pushed out version 1.3.16 to update the rewriting to leave canonical 
   urls unchanged. Please let us know if you are still seeing any issue with the
   canonical urls on your website.
 *  Thread Starter [Jens Tonnier](https://wordpress.org/support/users/tonnier/)
 * (@tonnier)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679387)
 * Yeah! You guys rock, thank you 🙂
 *  [Daniel](https://wordpress.org/support/users/gabu69/)
 * (@gabu69)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679388)
 * But what about when site is totally moving to https ?
 * Can there be an option in the settings to rewritte/not_rewritte the cannonical?

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

The topic ‘HTTPS protocol rewritting NOT for canonical URLs’ is closed to new replies.

 * ![](https://ps.w.org/cloudflare/assets/icon-256x256.png?rev=2471183)
 * [Cloudflare](https://wordpress.org/plugins/cloudflare/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cloudflare/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cloudflare/)
 * [Active Topics](https://wordpress.org/support/plugin/cloudflare/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cloudflare/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cloudflare/reviews/)

## Tags

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

 * 10 replies
 * 5 participants
 * Last reply from: [Daniel](https://wordpress.org/support/users/gabu69/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/https-protocol-rewritting-not-for-canonical-urls/#post-5679388)
 * Status: resolved