WordPress.org
Get WordPress

Make WordPress Core

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#30535 closed defect (bug) (wontfix)

canonical issue

Reported by: AlexPaulC Owned by:
Priority: normal Milestone:
Component: Canonical Version: 4.0.1
Severity: normal Keywords:
Cc: Focuses:

Description (last modified by SergeyBiryukov)

WordPress 4.0 canonical was working brilliant.

Updating to 4.0.1 was creating a issue to the https websites I manage... There is no more force to https and also because my main url was with https my website was accessible via ​http://sitename.com and ​http://www.sitename.com + ​https://www.sitename.com ...

From SEO point of view this is a mega failure guys hopefully you will take care of it in the next release...

In the meanwhile I have reverted the wp-includes/canonical.php file from version 4.0 and work as it should again.

Thanks

Change History (4)

#1 @SergeyBiryukov
12 years ago

  • Description modified (diff)

Related: [28610], [30090].

#2 @johnbillion
12 years ago

  • Milestone Awaiting Review
  • Resolution → wontfix
  • Status new → closed

Thanks for the report AlexPaulC.

Unfortunately we had to revert this change because of problems with reverse proxies. See #29708.

I'm going to close this as wontfix in favour of #27954. I think making this behaviour opt-in is the only option and I'll hopefully look at it in 4.2.

#3 @AlexPaulC
12 years ago

  • Resolution wontfix
  • Status closed → reopened

Well John, that's not very encouraging for HTTPS users...

This should be added at least as a option somewhere... as you mentioned, an opt-in.

Basically this update could have hardly affected the rankings of my website and end up with 3 variants of my every single page in Google Index... I'm not really a fan of a canonical link tag, this is useful but not to be abused of...

As I said, at least is a single file I need to change so I will be staying with the canonical.php from 4.0 ... Is the first time in 2 years I have an issue on a update... and this is very annoying specially being on automatically update which I have now disabled.

I consider that this should be address faster that 4.2, at least in 4.1 ... specially that everybody is pushing towards forcing SSL now...

NB: I re-opened this just to grab your attention

Cheers

#4 @dd32
12 years ago

  • Resolution → wontfix
  • Status reopened → closed

For reference, in 3.9 http and https url's didn't redirect, 4.0 added it, 4.0.1 removed it after breaking sites which used HTTPS loadbalancers in front of a HTTP site (not as uncommon as you think, even Cloudflare allows this now)

The solution has always been to use a plugin such as ​https://wordpress.org/plugins/https-redirection/ (or ​https://wordpress.org/plugins/force-ssl/ )

As 4.1 is very near to release, keep an eye on #27954 for 4.2.

Last edited 12 years ago by dd32 (previous) (diff)
Note: See TracTickets for help on using tickets.