WordPress.org

Make WordPress Core

Opened 20 months ago

Closed 20 months ago

Last modified 20 months ago

#43288 closed defect (bug) (invalid)

HTTP to HTTPS redirect on standard install

Reported by: richardkentgates Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.9.4
Component: General Keywords:
Focuses: Cc:

Description

After installing WordPress from Instalatron/cPanel as an HTTPS site, the expected redirect from HTTP to HTTPS did not take place. I checked options in the DB and it was set to HTTPS. The WordPress URL and Site URL in Settings>General reflected HTTPS, but no redirect.

Using two fresh installs as a controlled test, I found that setting a Static Page as the landing page solved this issue and the domain was redirected to the HTTPS version of the website as expected.

No plugins were added aside from Hello and Akismet. The theme was Twenty Seventeen.

Change History (4)

#1 @johnbillion
20 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Thanks for your ticket @richardkentgates and welcome to WordPress Trac.

WordPress doesn't include any automatic HTTP->HTTPS redirection functionality on the front end, only in the administration area. This is due to problems that it causes with reverse proxy setups, for example those that sit behind a service such as Cloudflare. You should implement the redirect at the server level.

See #27954 for some discussion about introducing a constant to enable this functionality.

#2 @richardkentgates
20 months ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

This is a usability problem for those that do not write code and a maintainability problem for website managers where maintaining non-customized versions of sites are concerned. Performing the task in one way but not another is also an issue with consistency where expected performance is concerned.

I know your developers are busy and I'm looking at getting involved in the core as of today, but closing this ticket was inappropriate and a disregard for the usability of this platform by the average blogger or small business owner.

I am not well versed enough in the core to fix this for you so I have no choice to but to continue pushing this issue where I can until I find someone who will listen. They will, of course, tell me to report it as a bug, and I will, so you may see this reported again.

#3 follow-up: @ocean90
20 months ago

  • Resolution set to invalid
  • Status changed from reopened to closed

We're aware of the issue, we also tried it in [28610] but that didn't work well, see #29708 for background.

Reclosing as invalid since it's not a new bug. But feel free to comment on #28521 or #27954 if you have additional thoughts.

#4 in reply to: ↑ 3 @richardkentgates
20 months ago

Replying to ocean90:

We're aware of the issue, we also tried it in [28610] but that didn't work well, see #29708 for background.

Reclosing as invalid since it's not a new bug. But feel free to comment on #28521 or #27954 if you have additional thoughts.

Ok, the added information was helpful. I will follow up with the recommended reading and see where I can help. Is there not a way to close tickets as Duplicates and cite the originals as is done on StackOverflow? Just a thought. Thanks for the sense of direction. Hope I can help.

Last edited 20 months ago by richardkentgates (previous) (diff)
Note: See TracTickets for help on using tickets.