One of our internal apps are reachable via following, example domain name address:
https://some-addres.some-domain:8443
For all following cases:
- https://some-addres.some-domain:8443 (200 resp)
- http://some-addres.some-domain:8443 (307 resp pointing to https)
- some-addres.some-domain:8443 (200 resp)
We are ending up in correct, SSL-ed application page. However, when we try to reach it via IP address (let's assume 1.2.3.4) following happens:
- https://1.2.3.4:8443 (200 resp but with no SSL)
- http://1.2.3.4:8443 (no response, failed)
- 1.2.3.4:8443 (200 resp, but with no SSL)
I'm not a sysDamin, and basically I have no access to any configuration of this particular instance, I'm just curious, how it is possible, that Domain name and IP address that ultimately at the end are same thing can behave in such different way? Does it depend on server configuration or this is part of RFC/Some other spec?
Thank you for help!