SJS wrote: >.. > That's because that "Host:" line is how the webserver determines which > virtual host you're asking for.
Makes sense! > > [snip] >> I guess for a browser, you'd need another intermediary acting similar to >> wget with the header rewrite trick? Along the lines of a >> single-destination proxy, or some language like that? > > There are firefox extensions that claim to give you control over all of > the headers. Ahh, thanks. Found one called "modify headers" that works. For this case, I add a rule to modify the header "Host" to contain the (replacement) value remotehost.net, and then activate it (by opening the modify headers extension) just before connecting to localhost:8888. I explain that because with no syntax explanation or examples, it is possible to miss the significance of the data columns (Name, Value), which after an example do seem adequate. ;-) > > Setting up a proxy on the far end of the tunnel and telling ssh to use > the local end of the tunnel as a proxy *ought* to do the trick. Those > who play with this sort of thing routinely could probably even tell you > what tools to start looking at. > Yeah, I pretty much knew that, but was just interested in figuring out why it didn't work with the tunnel at my end. Thanks again, ..jim (get well soon!) -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
