Confused with 3 redirection methods

  • Resolved Lonifasiko

    (@lonifasiko)


    7 years, 10 months ago

    Hello,

    After installing the SSL certificate for my domain, installed and run Really Simple SSL plugin, with the default options that were checked (Internal WordPress 301 Redirection and Javascript Redirection). Everything worked fine, without any errors. Also re-configured everything in Google Search Console & Google Analytics.

    I’m happily seeing my site is now running smoothly under https, and that all redirections seem to work perfect (without .htaccess file being modified). Nevertheless, I wonder how heavy are these default two dynamic redirection options? Because I’m seeing even internal links that are still pointing to http resources (to other posts, photos, etc.) , are properly handled, I guess dinamically, by Internal WordPress 301 Redirection and Javascript SSL Redirection. I think I don’t really understand the difference between them.

    In fact, although all seems to work fine, I read you recommend the .htaccess redirection method (if you know how to go back, just in case). So, should I now try updating the .htaccess file with the option you provide in the plugin, along with a search&replace across the database? Doing this, could I get rid off (and uncheck) these two redirection options/methods?

    I would appreciate some light on these 3 redirection methods and their possible incompatibilities, as I’m a bit scared with these changes and their possible side-effects. Thanks very much your help in advance.

    Best regards,
    Miguel

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Mark

    (@markwolters)

    7 years, 10 months ago

    Hi Miguel,

    the plugin indeed offers three redirect options, this is done so a redirect to https:// can work on any setup and server configuration. The WordPress 301 redirect and Javascript redirect will always work since these redirects are handled by WordPress. The .htaccess redirect option will work if the server uses an .htaccess file. Since not all servers use an .htaccess file the option is disabled by default. If your server does use an .htaccess file we recommend to enable the .htaccess redirect option, it’s slightly faster then the other two redirect options. Once the .htaccess redirect has been enabled, the other two options can be disabled.

    Internal links are updated to use https://, this is not done by the redirect but by the built-in mixed content fixer. The mixed content fixer takes a page, searches for all http:// references to your own domain, replaces them to https:// and then serves the page to your visitors. This is all done dynamically. Performing a search and replace on the database can be done but is not necessary for the plugin to function.

    Mark

    • This reply was modified 7 years, 10 months ago by Mark.
    Thread Starter Lonifasiko

    (@lonifasiko)

    7 years, 10 months ago

    Thanks for the clarifications Mark, greatly appreciated.

    Then I think I will try the .htaccess redirect option, and if works, I will disable the other two. Once selected, do I have to also check the option of not giving grant for editing the .htacess file?

    Regarding internal links, I finally yesterday performed a search & replace bulk action across the database to change all references from http to https. With this done, should I then disable the “mixed content fixer”, or it is still a good idea to have it working, just in case?

    Just in case it helps anyone, you can find the search and replace script I used for performing the changes here, as a couple of search and replace plugins I tried did not work for me.

    Thanks very much for your time.

    Miguel

    • This reply was modified 7 years, 10 months ago by Lonifasiko.
    Plugin Author Mark

    (@markwolters)

    7 years, 10 months ago

    The ‘stop editing the .htaccess file’ option can be unchecked, checking this will prevent Really Simple SSL from writing the redirect rules to your .htaccess file.

    Updating internal links in the database indeed makes the mixed content fixer obsolete. If all references to your own domain have been replaced in the database, the mixed content fixer doesn’t have to do anything anymore and can be safely disabled.

    Mark

    Thread Starter Lonifasiko

    (@lonifasiko)

    7 years, 10 months ago

    Thanks again for these two precious tips. I will proceed with the mentioned changes.

    Thanks and best regards,
    Miguel

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

The topic ‘Confused with 3 redirection methods’ is closed to new replies.

Tags