301 redirect only works on the front page

This seems to be the case with some hosting companies. As the redirect that was inserted in your .htaccess is works on all subfolders, this suggests your server does not recognize the /$1 that is used to redirect. You could try changing it into %{REQUEST_URI}

To change it, look for the really simple ssl comments in your .htaccess, and change the redirect rule to test.

As I can’t test it myself, I’d be interested to hear the results.

Like this?

# BEGIN rlrssslReallySimpleSSL rsssl_version[2.2.10]
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
</IfModule>
# END rlrssslReallySimpleSSL

Still giving 200 code when doing header response check.

I think the problem is in the server settings: here someone else encoutered the same issue.

I think I solved the problem finally.

I moved this code:

# BEGIN rlrssslReallySimpleSSL rsssl_version[2.2.10]
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
</IfModule>
# END rlrssslReallySimpleSSL

Up in the top of the .htaccess file before

# 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

Should there be any problems about having the SSL code before the WordPress code in the .htaccess?

Now I get these header responses.
1. https://trainingandrehab.dk/ redirect to https://trainingandrehab.dk/
2. https://trainingandrehab.dk redirect to https://trainingandrehab.dk/
3. https://trainingandrehab.dk 200 OK
4. https://trainingandrehab.dk/ 200 OK
The last two should not both respond 200 OK, right?

For the subpages:
1. https://trainingandrehab.dk/kontakt redirect to https://trainingandrehab.dk/kontakt which redirect to https://trainingandrehab.dk/kontakt/
2. https://trainingandrehab.dk/kontakt/ redirect to https://trainingandrehab.dk/kontakt/
3. https://trainingandrehab.dk/kontakt redirect to https://trainingandrehab.dk/kontakt/
4. https://trainingandrehab.dk/kontakt/ 200 OK

It’s only put at the bottom to ensure all redirects have finished when the redirect to https takes effect, so moving above the wp rules shouldn’t be a problem.

Interesting result, I’ll look into it, see if I can use this. Thanks for your feedback.

No problem and thank you for the help ??

Do you have a solution on the problem with the homepage url that responds with 200 OK with https both with and without the / at end of the url?
I guess the one with a / at the end should redirect to the one without.

After checking a few other big websites I see that the url for the root of the domain should return 200 OK both with and without the / at the end.

Sorry for the trouble ??