Peter Vroegop wrote:
>
> I wonder whether someone could shed some light on this:
>
> I have a number of computers running win95/win98 on a LAN
> using TCP/IP. We
> are connected to the outside world via an ADSL (Nokia M10)
> modem which has
> a static IP address. I have setup a pinhole in this modem so
> it routes
> requests via port 80 through to one of the machines on the
> LAN which has a
> web server running (internal IP address of this machine is
> 192.168.0.21,
> listening on port 80 as well).
> I have two domain names, call them "www.aaa.com" and
> "www.bbb.com" which my
> ISP points to the static IP address of the ADSL modem.
>
> Everything works of sorts , but whether a surfer tries to connect
> "www.aaa.com" or "www.bbb.com" you get the index page for "www.aaa.com" in
> both cases, so "www.bbb.com" just gets ignored.
> Any suggestions to fix this are most welcome.
> Also, once a surfer has connected to the site (either one) it shows in the
> URL bar of the browser the modems IP number (like "http://203.96.91.128/")
> rather than "www.aaa.com"
>
> On another list I have been told that this is caused because the DSL
modem
> is actually passing the HTTP requests to your internally masked server
> (private IP subnet) it is doing so by the older method (HTTP/1.0?) of
> using the IP address and NOT the hostname.
>
The Nokia works at an IP level, it knows nothing of HTTP internals. The NAT
should rewrite the packet IP source and destination addresses in the IP
header, not the HTTP header which is further down in the packet.
It doesn't act as an HTTP proxy.
I'd be interested to see a trace of the conversation to see if this is
really the case.
One question: Can your webserver resolve it's own name from an internal DNS?
> Since the HTTP requests are
> made by IP address the Web server has no hostname for which to match up
> against therefore it chooses the default vhost (i.e. aaa.com). This same
> behaviour occurs with clients running older web browsers which also
> request by IP (instead of hostname), even on servers NOT behind a
firewall. I
> believe this was an HTTP/1.1 thing that allowed HTTP requests by hostname.
Any suggestions to remedy this are most welcome.
Peter Vroegop
This message is part of the NZ Broadband mailing list.
see http://freebsddiary.cx/adsl/ for archives, FAQ,
and various documents.
To unsubscribe: send mail to majordomo@freebsddiary.cx
with "unsubscribe adsl" in the body of the message
This message is part of the NZ Broadband mailing list.
see http://freebsddiary.cx/adsl/ for archives, FAQ,
and various documents.
To unsubscribe: send mail to majordomo@freebsddiary.cx
with "unsubscribe adsl" in the body of the message
Received on Thu Jul 6 11:13:35 2000