Wordpress 4 accessible from http and https with WP Supercache enabled

0

I am trying to enable a web with Wordpress 4 access to it from http and https, customer demands. I have already installed the certificate and it is working, but I am not sure how to perform the part in which it resolves from the two protocols.

I have the WP Supercache plugin enabled on the web and I would like to know if someone has had to do something similar and how it has been resolved.

I'll give you some references I've found in case I'm on the right track or not:

link link

At the moment, what I need is that http://www.midominio.com and https://www.midominio.com are navigable. Currently they are but several urls from https point to http and the certificate shows me which parts of the web are not safe. How can I solve it?

    
asked by David V 22.11.2016 в 18:13
source

1 answer

0

First of all, you have to make your client understand that it is always better https than http and that there is no sense of any kind "keep" both.

Theirs is to always use https .

Now, why can not Wordpress be done? I explain it to you:

Wordpress saves BBDD of% complete% ( URL for example) in both% of the pages as of the post. That is, every time Wordpress paints the http(s)://midominio.com/contacto what it does is put the URLs that it has in HTML , for that reason there are only two options (always keeping in mind that we do not force any of the two versions):

URLs in BBDD as BBDD

  • If you enter from https the first load you should do it correctly, but all the URLs that the page will have will be via http so the following jumps will take you to the secure version, since e as well as is in https
  • If you enter from BBDD the behavior is the normal of a https with Wordpress

URLs in https as BBDD

  • In this case, if we enter via http we will give a problem that https since the URL will be contenido mixto but some of the resources are being served with https and that is a failure of security and it is more than likely that the web is not seen correctly. Also most likely we jump to the version http as soon as we click any link.
  • If you enter from http , the behavior is normal for% normal% co.

As I mentioned above, the best is always http . What happens to your client to want both? It may be more a question of doubts / understanding than anything else.

    
answered by 30.11.2017 в 13:07