Https redirect was set in javascript

I’d have to see the site, could you send me the url by mail? rogier /at/ rogierlankhorst.com

Hi RogierLankhorst, I am having this same issue. I will email you as well.

Thank you,

Julien Kos

Hi everybody,
There’s a simple workaround:
First check using a ftp client (FileZilla is a very good choice) your .htaccess file access right and set them 0644 in order to edit and save any change made in the file.
The following lines are automatically set by WordPress in a .htaccess file, created if none found, in order to have the permalink working:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

So, simply edit your .htacces file and add bellow the following lines:

# BEGIN rlrssslReallySimpleSSL rsssl_version[2.1.18]
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
</IfModule>
# END rlrssslReallySimpleSSL

Most important let .htaccess file access rights set to 0644. When set bellow this, like 0404 for instance, which is far better, the plugin can’t check your .htaccess file and therefore decide to use javascript instead.
That’s all.
Gilles

P.S.: to Rogier: please think in the next version to first check the .htacces rights level, before enacting javascript redirection

Thanks for the feedback. Permissions were already checked, but only since 2.2 is there a difference in notification between failure of the redirect test, and failure to write the htaccess.

In the above cases the htaccess was writable, but the server configuration caused the redirect test to fail. In those cases the server variables are not passed, so the redirect condition is never met. This would result in a redirect loop. Therefore the redirect won’t be set in htaccess.

You are welcome Rogier.
You are right regarding the permissions check (last plugin version 2.2.6 in use).
I’ve just changed my .htaccess permissions to 404, which I have rather keeping, and the .htaccess configuration was positively detected! Up to now I had to shift through ftp from 644 to 404 ad reverse from 404 to 644. Thanks!

If I may, have you ever heard of any kind of interaction between the PHP allow_url_fopen directive and your plugin?
My webhoster sees the directive set to true (both local and master) but my website -through phpinfo()- sees it set to false (both local and master). I’ve been said that it was due to the fact that from my webhoster side the test was made through http connection when from my website it was made through https connection. If so I should have the local directive set to false and the master set to true.
I wonder if it is a false positive answer, I mean it is set to true but wrongly detected, or if the plugin does interact in anyway and changes the directive values.
Thanks in advance for your kind help.
Regards.
Gilles

Hi Gilles,

allow_url_fopen is a setting that can only be changed in on the server level, not in a php script.

Testing through http or https can make a difference, so I think that is probably the cause.

Rogier

Hi Rogier,
Thanks again for the clue. That’s what I was guessing.
Regards.
Gilles

So is this the full code that should be in the .htaccess file? I’ve tried this and it just causes “ERR_TOO_MANY_REDIRECTS”.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

# BEGIN rlrssslReallySimpleSSL rsssl_version[2.1.18]
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
</IfModule>
# END rlrssslReallySimpleSSL

If the redirect rule the plugin generates causes redirect rules, you could try different redirect rules, I’ve described some options here.
https://really-simple-ssl.com/knowledge-base/manually-insert-htaccess-redirect-http-to-https/