[wp-trac] [WordPress Trac] #51437: Streamline migrating from HTTP to HTTPS

[WordPress Trac]

#51437: Streamline migrating from HTTP to HTTPS
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  flixos90
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.7
Component:  Security                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note                                           |
-------------------------------------------------+-------------------------

Comment (by flixos90):

 @johnbillion I think in this case the URLs in WordPress should still be
 using HTTPS, or not? If the site can be accessed using HTTPS, its links
 should also rely on HTTPS - why would we want to keep them HTTP in that
 scenario?

 I see how technically, without the reverse proxy of course it wouldn't
 work anymore, but I think disabling that would have similar implications
 like e.g. the server's SSL certificate becoming invalid.

 I may not fully understand your point, in that case could you elaborate?
 From what I'm thinking, this ticket shouldn't be affected by how exactly
 HTTPS access is implemented for a domain. It's primarily focused on making
 sure in such a case all site-owned URLs use HTTPS to avoid mixed content
 automatically where possible, without requiring the user to do a DB
 search-replace.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51437#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform