[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Sorry if I'm long-winded - With regards to the virtual hosting and the webmail - The webmail server is seperate from the apache virtual hosts. The webmail sits on a domain member server. Internally the webmail resolves fine and (Mdaemon+Worldclient) comes through over normal http. It works fine internally with vhosting. Externally with vhosting all is getting hijacked by the webserver. I just realized I can restrict Mdaemon webmail to use a secure port. It'll be a pain to retrain users though. User types in www.myschool.org DIY DNS redirects to 80.x.x.x:443 Gateway sees its https and sends to 172.x.x.webmail User types in secret.myschool.org DIY DNS redirects to 80.x.x.x:80 Gateway sees https traffic and sends to 172.30.20.website It is when I enable virtual hosting the website/server latches on to *all* http traffic. I have tried restricting the vhosts to listen on an ip, but when I do that I can only get one (the default) website to resolve. I guess I am more concerned about getting *just* the website resolving nicely on both sides simutaneously. I can shift all the email/webmail to secure traffic/ports. On 3/8/06, Robin Cornelius <robin@xxxxxxxxxxxxxxxxxxxxx> wrote: > Kevin Tunison wrote: > > Hello all, > > > When I enable virtual hosting all is fine internally. The port forward > > seems to not work when I have virtual hosting on, in that the webmail > > server (https) is not accessable, instead http traffic appears (our > > website). > > Hi Kevin, > > Is the problem that when you access the https webmail site with virtual > hosting enabled that you are not requesting the website by a domain name > and end up just getting the default virtual host on the system (the > first one listed). > > Ie you need to access the server via an address such as > https://squirrel.mydomain.com *even* if squirrel.mydomain.com resolves > to the public ip of the gateway. That way when the gateway forwards the > (https) request the header contains squirrel.mydomain.com and apache > knows which virtual host to serve. > > If you do set up squirrel.mydomain.com to resolve to the public ip of > the gateway then this must only be done on the external DNS servers, on > the intranet set squirrel.mydomain.com to resolve directly to the web > server on the local network. This way users use a consistant method to > access the site either local or remote. > > Probably got the wrong end of the stick here and misunderstood the > problem :-) > > Regards > > Robin > > -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html