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

Redirecting http to https on non-standard ports

Hi,

I've been trying to setup a a web application behind a Sophos software appliance on a non standard https port.
It work perfectly when I was using port 443. I trying to move the application to port 4443 (or any other non standard https port), however I having trouble with 302 HTTP Redirects. The link in the location header is not being rewritten to https.
I've come across some bugs id, but there aren't any explanations (on the bugs):
ID34154 WAF https/s redirection does not work with non-standard ports (Fixed in:9.308)
ID31443 9.202 WAF: HTTP/S redirection does not work with non-standard ports (Not Fixed?)

I'm using version 9.310-11.

Thanks

This thread was automatically locked due to age.

0 BAlfson over 9 years ago

Hi, Paulo, and welcome to the User BB!

4443 is reserved in the UTM. Are you trying to get the Virtual Server to redirect Example Domain to https://example.com:3333/?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 abdulpaulo over 9 years ago in reply to BAlfson

Hey Bob,

I think the one reserved is 4433.
The website is working.
I have a virtual server on https://mydomain.com:4443/ (And it's showing my homepage) pointing to an internal server.
When I try to access one of the links that require authentication and thus my website redirects the unauthenticated user to the login URL (using a 302 HTTP Response), I believe the reverse proxy isn't handling this correctly as it redirects me to http://mydomain.com:4443/login instead of https://mydomain.com:4443/login

If I use the default https port (443) the site works normally (even on a 302 http reply).

Thanks !
Cancel
Vote Up 0 Vote Down

Cancel