I am using the latest RC4 and have the following issue.
I am using the Reverse Proxy-Feature and have the current environment:
Server2: A Windows Server with Tomcat (not my one ) that has a website on port 80 in a path named /crappyname (http only).
What I want to do:
I am accessing the Internet and all HTTP(S) traffic is directed to my Server1 (Nethserver). On my Nethserver my homepage www.company.com is running with SSL enforcing enabled. Now I want to open https://company.com/portal that should show me what I can see internally on http://server2/crappyname.
So there are 2 things:
- Add the SSL encryption to the Internet
- Use a simple name (/portal) instead of a complicate one (/crappyname).
What I did:
- I enabled the “Reverse Proxy” Feature via Software Center
- Configured the following at “Reverse Proxy” Feature:
– Name: portal
– Target: http://10.11.12.13:80/crappyname (IP of the internal server)
– Require SSL Connection: active
– Description: Crappyname Portal
What I have now:
I open https://company.com/portal and after some time (I assume the Chrome timeout) I have in my address field http://10.11.12.13/crappyname - what the target is.
Is the Reverse Proxy the wrong solution for this? If yes: what is it for - maybe I have a missunderstanding of that phrase. If no: what can be the bug?