Trailing slash redirects not working in https - working in http: What might be the culprit?

Who's "we"? You got a mouse in your pocket?

How many redirects do you want?

You can do 3,2, or 1.

One is better, but most use the 2 redirect solution.

One is better because who knows how many redirects google actually follows, and, why keep the visitor in suspense any longer....Sure, internet is fast these days...but who knows what the end user has...

There are complete codes for htaccess online if you google it.

------sample code below-----

RewriteEngine on

RewriteCond %{REQUEST_URI} /(.+)/$
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^ https://www.example.com/%1 [R=301,L]

RewriteCond %{REQUEST_URI} !(.+)/$
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+)$ https://www.example.com/$1/ [R=301,L]

RewriteCond %{HTTP_HOST} !^www\.(.*)$ [OR,NC]
RewriteCond %{https} off
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]


Only one 301 for each combination of www, https, or slash!

I'd do all 3 cases, but each filter gives one 301.

Just put your own domain in place of example.

Paul