Hello.
When I use the DNS with the HTTPS scheme and the path located on the WAS (both internally and externally) I get the Page Cannot be Found Error. Although I am able to hit it properly when I use the internal IP address. Despite this I can still hit the default HTTPS page without a problem when I use the DNS (both inside and outside of the firewall).
Regardless of using the DNS or the IP, externally or internally I know that I am hitting the HTTPS because the Certificate request pops up (and I can view the default page). But somehow the HTTPS is not directing the traffic to the Application Server properly (even though using the internal IP address and port (443) for the HTTPS actually hits the Application Server and the pages work properly).
I'm pretty stumped right now so any suggestions would be appreciated.
Craig Pettie
When I use the DNS with the HTTPS scheme and the path located on the WAS (both internally and externally) I get the Page Cannot be Found Error. Although I am able to hit it properly when I use the internal IP address. Despite this I can still hit the default HTTPS page without a problem when I use the DNS (both inside and outside of the firewall).
Regardless of using the DNS or the IP, externally or internally I know that I am hitting the HTTPS because the Certificate request pops up (and I can view the default page). But somehow the HTTPS is not directing the traffic to the Application Server properly (even though using the internal IP address and port (443) for the HTTPS actually hits the Application Server and the pages work properly).
I'm pretty stumped right now so any suggestions would be appreciated.
Craig Pettie
