[ previous ] [ next ] [ threads ]
 From:  Joey Morin <jmorin at icomm dot ca>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] NATed services by the public IP
 Date:  Fri, 25 Jun 2004 15:01:37 -0400 (EDT)
This one time, at band camp, Adam Nellemann said:

> The (most likely) reason your http server wants to know its domain name,
> would be in case you run more than one server on a single machine
> (and/or if you have more than one domain, run by server(s) on a single
> machine). In this case, the web server would need to know which http
> requests it should handle (being the ones with a destination domain
> matching the one you entered!)

perhaps.  but what's looks like is happening here is that the webserver is
checking for the existence of index.html by becomeing an http client for a
moment, and making a connection via the gateway back to the same url that
was requested of it.  the idea being that if it doesn't exist, it will
dynamically build an index.html containing a list of files.  however,
since you can't reach a nated service from the inside, that fails.  very
strange.  if index.html does NOT exist, all works fine.  if it DOES exist,
it craps out.