On Wed, Feb 18, 2009 at 7:35 AM, KURT PETERS <peterskurt@xxxxxxx> wrote: > Thanks for your help. The *:80 method seems to work. Just have 2 follow-up > questions: > > 1) Did I need to put the Listen 443 AFTER the </VirtualHost> for the 80 and > 8080? In other words, does apache2 do the parsing of virtual hosts and > "listens" in order? No. You can safely put all the "Listens" up front. > 2) I use godaddy's forwarding feature for my domain name <whatever.com> > does anyone know why I have to use the actual IP address when I want to get > my web server to respond to anything other than the port 80 at > <whatever.com>? For instance, if I type in <http://www.myserver.com:8080> > it does not work, but if I use <http://172.20.30.40:8080> it does! > I'm wondering if this is a godaddy problem or my Apache2 set up. It's a "GoDaddy" problem. The way their forwarding works is that they set up a virtualhost with your domain name on one of their servers, and forward all requests. But they only do this for port 80. You need to make whatever.com point directly to your IP, in stead of using a forwarding service. If your IP is dynamic you could use a service like zoneedit.com. I've been using them for ages now for my homeserver. Krist -- krist.vanbesien@xxxxxxxxx krist@xxxxxxxxxxxxx Bremgarten b. Bern, Switzerland -- A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? A: Top-posting. Q: What's the biggest scourge on plain text email discussions? --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|