> > On 6/13/07, Aaron <[EMAIL PROTECTED]> wrote: > > > No multiple IPs on the outside. I would just do a 1 to 1 nat if that > > > were the case.
> On Wed, 2007-06-13 at 09:14 -0400, Joshua Slive wrote: > > You're screwed then. You can't do IP-based virtual hosting with only a > > single public IP. On 14.06.07 16:00, Nikolai Lusan wrote: > Well actually you can e.g.: > > NameVirtualHost my.ip:80 > NameVirtualHost my.ip:443 > > <VirtualHost my.ip:80> > SiteName site1.dns > </VirtualHost> > <VirtualHost my.ip:80> > SiteName site2.dns > </VirtualHost> > <VirtualHost my.ip:443> > SiteName site1.dns > </VirtualHost> This is NOT ip-based virtual hosting, this is name-based virtual hosting. > This is quite valid with only 1 public IP. The issues with ssl is that > you can only do one site per public IP Actually, you can have one SSL certificate per IP/port combination. You can run apache on more ports on one IP and more hosts (using the same SSL certificate, e.g. wildcard) on each port. Although neither one is generally recommended, they both _can_ work correctly. -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Quantum mechanics: The dreams stuff is made of. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
