On Tuesday 02 January 2007 10:00, [EMAIL PROTECTED] wrote: [snip] > > This key is: > > > Your router only forwards to addresses and ports. It knows nothing of > > > the protocol you're forwarding. > > > > If the router is addressed as tigger.ws, deej.tigger.ws or > > sunfeathers.net it forwards the request to 192.168.5.254 and the same > > page is served. > > > > Am I missing something ? > > Thanks > > James > > I don't think so, you've given a quite detailed account of the > problem, the root cause of the problem, and the solution. > > As you've described the router is doing a portforward at the TCP > level, where it can only look at IPs and port numbers. You only have > one IP, and only one port. Tigger used to do proxying at the HTTP > layer, where it was looking at the "HOST: " field of the HTTP request > - there can be lots of different "HOST: " fields. > > You've already described the solution you had on the past: Tigger > obviously knows how to do the right proxying. Just get your router to > point to Tigger (or some similarly configured HTTP proxy, if Tigger > doesn't do what Tiggers do best any more) and everything should be > fine.
<blush> after reading this 10 times I still am not sure what this means ... > Just get your router to > point to Tigger James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
