99bet login register.Enjoy Free 888+200 Daily Legal Bonus

Resolved curve
(@curve)

5 years ago

I’m trying to do all the redirects in the topic title, but failing at the moment!

In redirection site settings I have both ‘Force a redirect from HTTP to HTTPS’ and ‘Add www to domain’.

Is it possible to pass the URI in a domain as well? For example, I want someone who browses to https://<domain>/<URI> to be redirected to https://www.<domain>/<URI>.

Everything I’ve tried so far results in redirect loops or a redirect to https://www.<domain> without the URI

Thanks

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

Plugin Author John Godley
(@johnny5)

5 years ago

That is how it is supposed to work. Can you give a real example of something that isn’t working?

Thread Starter curve
(@curve)

5 years ago

Hmmm, thanks @johnny5. This lead me to try to recreate on a dev server and it works as intended. I think I may have a misbehaving production config. I’ll update this post if relevant.

Thread Starter curve
(@curve)

4 years, 10 months ago

Hi @johnny5, I’m still having issues with this.

The server I have everything working on is running apache, whilst the server with issues is running on nginx. I’m not sure if its relevant, but the domain name begins with a number, which seems to cause issues with the UI as you can see on this screenshot – I don’t know if this is involved in the issue.

On the apache site the following redirect correctly to https://www.domain/trailingURL:

https://domain/trailingURL
https://www.domain/trailingURL
https://domain/trailingURL

On the nginx site, the following happens:

https://www.domain/trailingURL correctly redirects to https://www.domain/trailingURL

https://domain/trailingURL and https://domain/trailingURL both have the trailingURL stripped and are redirected to https://www.domain/

Please let me know how I can troubleshoot the issue.

Thread Starter curve
(@curve)

4 years, 10 months ago

Posting an update in case anyone else has the same issue – looks like the problem was upstream domain config rather than anything to do with the plugin!

Once we’ve fixed that I don’t know if the UI issues would cause further problems, we’ve made some changes in the server lighttpd.conf file in the initial effort to solve this…

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

The topic ‘Redirect to HTTPS, www AND URI?’ is closed to new replies.