|
The Virtual Hosting referred to here (I think) is for those cases where you want to automatically give everyone their own web-site automatically without setting each site up in the config file. Each site gets treated as separate but uses the template design of the virtual hosting section of the config document. This is the kind of stuff ISP's use to provide everyone with their "own web site". There is an Apache red book that explains this better than I have. regards Evan Harris <SNIP>
> What I mean by virtual hosting is having multiple > domains, each with their > own unique configuration, but running on the same server > instance. Oh yeah, > they all come into the same port number and all of these > are managed in the > same httpd.conf file. One instance, one conf file, one > port, unlimited > domains, unlimited configurations. This is one of the > major reasons Apache > is so popular in the web world (and coming soon to a 400 > near you!) > You can do this with classic already, just as you explain. Of course, I prefer having a seperate config for each web instance, which both can do. And on the 400 the ability to assign multiple IPs to a single interface makes it a no brainer. And I thought pbA could do this already, but maybe not. I know the *nix version can.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.