Victor Rehorst wrote:
>> I tried NetHopper 3.2 myself just this weekend, and what I found
>> was that it doesn't seem to send the host field when it requests a
>> page, so
> Yes, this was part of HTTP 1.1.
But NetHopper DOES appear to send a "Host:" line!?
>> that servers that do single-IP virtual hosting just serve it up the
>> default domain rather than the requested domain. Is this the case,
>> or am I perhaps missing part of NetHopper?
> No, there's no part that will fix it, you are in fact getting the
> "full NetHopper Experience" :)
Again, see my other post. This works for me. As the actual example... I run
a site called "Boob! Dreamcast Research" at www.boob.co.uk. www.boob.co.uk
actually resolves to 184.108.40.206 -- which reverses to thegypsy.com --
another site of mine. Now, if you use a normal browser and go to
220.127.116.11 (i.e. by IP, no host name given), you will get the stuff at
thegypsy.com, of course.
If I go to "www.boob.co.uk" with NetHopper, I DO get the proper Boob virtual
host. I do NOT get thegypsy.com as I would if it was only IP. I'm running
Apache and it obviously sees the "Host:" line that NetHopper is sending and
gives the proper virtual host.
Now, maybe it isn't quite standard or something -- and that is why the other
guy's isn't working. Maybe Apache handles it a little better or something
than whatever his server is running.
Oh bah. After writing on that it suddenly dawned on me. I'm going through a
proxy server. heh. It must be sending the proper HTTP/1.1 request out, eh?
Heh -- sorry about that. Now it all makes sense. :)
-- Read the List FAQ/Etiquette: http://www.newtontalk.net/faq.html Read the Newton FAQ: http://www.guns-media.com/mirrors/newton/faq/ This is the NewtonTalk mailing list - http://www.newtontalk.net
This archive was generated by hypermail 2.1.2 : Tue Apr 02 2002 - 14:02:32 EST