|
Wayne <wayne@xxxxxxxxxxxxxxx> wrote:
> >So if I have secure.foo.com as my https address, and on the back end, there
> >is web1.foo.com, web2.foo.com, and web3.foo.com. In the www server
> >configuration, is there anything special that has to be done so that the
> >certificate (which is made for secure.foo.com) is handled correctly for the
> >named virtual server? (Assuming Apache as the www server)
>
> Nothing special, configure each Aparche server to have secure server
> running, and install the key to every one of them. The validation of the
> SSL key is at the client side, not at server side. To the server, it does
> not care what itself is being called.
Almost, but when Apache generates redirects, it uses its hostname which
would prevent your balancing from taking place and would cause SSL
warnings at the client side (requests get for example redirected directly to
machine1.foo.com). See/set the configuration parameter
"UseCanonicalName Off".
Regards,
Axel Dunkel
---
Systemberatung A. Dunkel GmbH, Gutenbergstr. 5, D-65830 Kriftel
Tel.: +49-6192-9988-0, Fax: +49-6192-9988-99, E-Mail: ad@xxxxxxxxx
|
