Olivier,
Marking off-topic because this is about Apache httpd and not Apache
Tomcat, but it's fine.
See below.
On 3/26/22 07:48, olivier giorgi wrote:
The goal is that users willcontinue to connect to "https:/server1"but will actually
browse to "https://server2".
I have successfullyredirected from "server1" to "server2" via apache/http, but
the url seen in the browserchanges.
In the following configuration, how can I make this redirectioncompletely
transparent to end users? <VirtualHost*:443>
ServerNameserver2
ServerAliasserver2
ErrorLog"C:\Apache24\logs/Error.log"
TransferLog"C:\Apache24\logs/access.log"
LogLevelwarn
SSLEngineon
SSLProxyEngineOn
SSLCertificateFile"E:\certificat\proxy\server2.cer"
SSLCertificateKeyFile"E:\certificat\proxy\server2.dsone.3ds.com_self.key"
ProxyPass/3dpassport "https://server1/3dpassport"
ProxyPassReverse /3dpassport "https://server1/3dpassport"
</VirtualHost>
You're on the right track, here, but it's not clear which server's
configuration file is being shown above.
If you want users to type "server1" but the information really comes
from "server2", then you want to configure server1 like this:
<VirtualHost *:443>
ServerName server1
ServerAlias server2
...
ProxyPass /3dpassport https://server2/3dpassport
ProxyPassReverse /3dpassport https://server2/3dpassport
</VirtualHost>
This will configure server1 as a reverse-proxy for server2, but only for
the /3dpassport URL-space. If you want to proxy *everything*, you can just:
ProxyPass / https://server2/
ProxyPassReverse / https://server2/
Hope that helps,
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org