Awie wrote:
> John Saunders told me that most of WEB (the require authentication) need
> same IP. I must forward the SSL packet to Squid as well as HTTP. His
> suggestion is very logical. However, when I tried to do it by adding the
> command into my Cisco IOS. My browser goes "freeze" until it reach the
> timeout and displaying error message.
This is true for quite many services where authentication is performed
using cookies.
What most people recommend it to use masquerading/source NAT to have the
client address rewritten to that of the proxy.
Theoretically it should also be possible to use a TCP proxy capable of
running as a transparent proxy. I think there is patches to plug-gw from
TIS FWTK for this...
> Again.....if I run non-transparent mode (I put same proxy address and port
> in my browser for all protocols; HTTP, FTP, SSL, etc), it runs very well. I
> assume that in my non-transparent proxy, all requests (FTP, HTTP, SSL) is
> forwarded to Squid. Am I right?
Your browser does what you tell it... so yes.
> I posted this problem to Squid's user mailing list and send mail to several
> people that seems expert (including you). Unfortunately, so far I still get
> no solution. Because I cannot "isolate" the source of problem, yet.
You quite likely have isolated the source already.
/Henrik
-- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Tue Oct 17 2000 - 22:17:34 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:55:46 MST