On Wednesday 14 January 2004 01:47 pm, Jeff Newmiller wrote: > > > > > > Not so -- you can use policy routing to redirect the requests to the > > > Squid server; that preserves the original source IP address. See > > > http://www.shorewall.net/Shorewall_Squid_Usage.html > > > > > > -Tom > > > > Ah yes, I'd forgotten about using policy routing for redirection. Does > > this provide the information required by the original poster, including > > the full URL of the request? > > No, policy routing pays no attention to URLs. It works through tcp/ip > information, such as ip numbers and protocol numbers. > > Fortunately, the transmitted header of the http request normally does > include the URL of the request, and the Squid instance receiving the > connection is designed to interpret that header. > > I would suggest that the Squid instance be installed on a computer that is > not the router (presumably one in the private network)... this will > eliminate the concern for squid compatibility with the router software and > hardware (hard disk). The policy routing would have to include a special > provision for the squid computer to make http connections to avoid a > communication loop.
The instructions at the URL that I provided above include such a safeguard. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
