Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 2 subscribers
  • Views 9752 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HTTP Redirect

JeffreyCase
Hello All,
I have searched for countless hours and am unable to find what I am trying to do.  I am wanting to make all HTTP traffic get redirected to HTTPS.  I have looked at DNAT, SNAT, etc and nothing I have tired seems to be working.

Scenario:
User browses to http://www.weather.com and i want that webpage to be changed to https://www.weather.com without the user remembering to put https to get the secure website.

I am looking to go this path so I can block all HTTP traffic and just allow HTTPS since websites will automatically be converted over to HTTPS without user intervention.

Everything I have read says you need a webserver to do this and I am having a hard time believing there is no way to say "port 80 change to port 443".

https://www.sophos.com/en-us/support/knowledgebase/120388.aspx


This thread was automatically locked due to age.
Parents
  • 0
    [...] at present, it has to be done by the webserver.

    Agreed, and that seems like a UTM feature request that would always remain on the back burner.  I can see the web Proxy testing HTTPS for a new FQDN/IP, caching the result for four hours and then switching to HTTPS for its requests to the server.  Doesn't seem that difficult.

    Cheers - Bob
Reply
  • 0
    [...] at present, it has to be done by the webserver.

    Agreed, and that seems like a UTM feature request that would always remain on the back burner.  I can see the web Proxy testing HTTPS for a new FQDN/IP, caching the result for four hours and then switching to HTTPS for its requests to the server.  Doesn't seem that difficult.

    Cheers - Bob
Children
No Data