Friday, January 28, 2005 Hi Aparajita,
Many thanks for your prompt reply! > Make sure your DNS servers are set up to redirect > site1.com to www.site1.com, or add another entry in virtualhosts.ini > for site1.com I don't know who has control over the DNS entries, so easy enough to just add the sites to virtualhosts.ini. Thanks for the tip! > Your suggestion of an entry in virtualhost.ini for the raw IP address > seems to be the best solution. In addition to the warning, you might > consider adding a prompt to ask them which site they wanted to go to > and give them links. Great idea! Actually, they may be hosting different sites for different clients on the same server, and may *not* want someone to see all the clients being served up by this computer. Although someone probably can figure it out by other means, probably they wouldn't want it to be so easily advertised to the users who's all being hosted... :-) > I'm not sure about that, but I think 4D decrypts the request _before_ > it gets to On Web Connection, which means it is decrypted before it > gets to Active4D, which means virtualhosts.ini will work. Cool! Guess we'll find that one out once we get to SSL (initially we won't need it, but it likely will come up on a future project). If it does work, then this gives Active4D/4D a feature that IIS doesn't have! :-) >> 4) Also, isn't the SSL certificate tied to a specific domain (ie, >> "www.site1.com")? So how does it work even in a multihoming situation? > > Not sure, maybe someone else can answer this. Anyone else have any experience with this? Would be good to know, as I'm sure someone's going to ask me... Thanks again! Michael Larue -------------------- > From: Aparajita Fishman <[EMAIL PROTECTED]> > Reply-To: Active4D Developer Discussion List <[email protected]> > Date: Fri, 28 Jan 2005 18:04:07 +0000 > To: [EMAIL PROTECTED] > Subject: Re: [Active4d-dev] Multihoming and host headers > >> 1) Do I simply configure the VirtualHosts.ini file exactly the same as >> indicated in the instructions? (I would guess yes, but I'm not totally >> clear >> on this.) > > Yes, use the hostname field to resolve between www.site1.com and > www.site2.com. Make sure your DNS servers are set up to redirect > site1.com to www.site1.com, or add another entry in virtualhosts.ini > for site1.com. > > >> 2) What happens if someone enters >> "http://192.168.1.7/innercontents/innerfile.html";, and that path >> happens to >> be valid in two different sites? (ie, >> http://www.site1.com/innercontents/innerfile.html and >> http://www.site2.com/innercontents/innerfile.html both exist). How does >> Active4D resolve this? Would the way to avoid this problem be to force >> the >> user to use a host name in their request, and set up an entry in the >> VirtualHosts.ini for the IP address in the Host Name column to direct >> this >> request appropriately (ie, some page that says "please use the site >> name in >> your url?")? > > If they use an IP address in the browser and you have multiple sites > with the same URL on the same IP, you have to do something to prevent > this, because there is no way for the poor server to magically know > their intention. > > Your suggestion of an entry in virtualhost.ini for the raw IP address > seems to be the best solution. In addition to the warning, you might > consider adding a prompt to ask them which site they wanted to go to > and give them links. > > >> 3) What about SSL? Reading up on host headers and the IIS server, it >> appears >> this doesn't work (see http://support.microsoft.com/?id=187504). I >> would >> think the same problem applies to 4D/Active4D? > > I'm not sure about that, but I think 4D decrypts the request _before_ > it gets to On Web Connection, which means it is decrypted before it > gets to Active4D, which means virtualhosts.ini will work. > > >> 4) Also, isn't the SSL certificate tied to a specific domain (ie, >> "www.site1.com")? So how does it work even in a multihoming situation? >> Isn't >> there just one certificate for the web server? (Or once you have the >> SSL >> certificate set up, it doesn't matter what the incoming domain is?) > > Not sure, maybe someone else can answer this. > > Regards, > > - Aparajita > > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev > Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ > _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
