You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Joe Brenner <do...@kzsu.stanford.edu> on 2001/12/06 03:52:06 UTC
[OT] Re: Multiple Sites
"Andy Sharp" <as...@nector.com> wrote:
> As others have aluded to, if you're trying to serve
> multiple domains (or hostnames) off one IP, you use a
> system called software virtual hosting. HTTP/1.1 Supports
> the Host: field in the http header to resolve to the site
> domain.
There's a limitation on virtual hosts though, if you want to
do any kind of ecommerce stuff with SSL (which works via the
IP number), it won't work if you try to do it with more than
one of the vhosts.
So you're clients are going to be stuck using an external
agency (like paypal?) if they want to take on-line
payments.
(Though, it's always seemed to me that it might be a decent
design to have *one* vhost dedicated to accepting payments
for the other vhosts... so when the user is ready to close
the deal they get kicked to "payment.super_secure.com" where
they're asked for the credit card info to finish
processing).
Re: [OT] Re: Multiple Sites
Posted by Wim Kerkhoff <wi...@merilus.com>.
Joe Brenner wrote:
>
> "Andy Sharp" <as...@nector.com> wrote:
>
> > As others have aluded to, if you're trying to serve
> > multiple domains (or hostnames) off one IP, you use a
> > system called software virtual hosting. HTTP/1.1 Supports
> > the Host: field in the http header to resolve to the site
> > domain.
>
> There's a limitation on virtual hosts though, if you want to
> do any kind of ecommerce stuff with SSL (which works via the
> IP number), it won't work if you try to do it with more than
> one of the vhosts.
Yeah, I've scratched my head on that issue before. Eventually I gave up
after reading the mod_ssl docs:
http://www.modssl.org/docs/2.8/ssl_faq.html#vhosts
The most common way to do it is to use IP aliasing to assign multiple
IPs to your server, once for each SSL vhost. I just did a search through
the apache-modssl mailing list, and you can actually do multiple unique
SSL name-based vhosts on the same IP, _if_ use use separate ports for
each. That might be acceptable as well... ie domain1.com is accessed via
https://domain1.com:1000, domain2.com is https://domain2.com:1001, etc.
http://marc.theaimsgroup.com/?l=apache-modssl&w=2&r=1&s=ssl+virtual+host+name+based&q=b
--
Regards,
Wim Kerkhoff, Software Engineer
Merilus, Inc. -|- http://www.merilus.com
Email: wim@merilus.com
Re: [OT] Re: Multiple Sites
Posted by ___cliff rayman___ <cl...@genwax.com>.
> (Though, it's always seemed to me that it might be a decent
> design to have *one* vhost dedicated to accepting payments
>
> for the other vhosts... so when the user is ready to close
> the deal they get kicked to "payment.super_secure.com" where
> they're asked for the credit card info to finish
> processing).
i have seen it done this way before. just got to make sure you
can identify the client since you will not get back a cookie for
your vhost. you will probably have to reset the cookie for the
domain of your isp, or pass as hidden data, or in the url.
http://www.mydomain.com/buystuffnow.html
https://www.isp.com/~mydomain.com/paymenow.html?sessionID=xyz987123456
--
___cliff rayman___cliff@genwax.com___http://www.genwax.com/