> -----Original Message----- > From: Listserv [mailto:SALISTSERV@xxxxxxxxxxx] > Sent: Wednesday, September 14, 2005 11:27 AM > To: Sturgis, Grant > Subject: RE: Problem logging in to webmail site > > > Using WCCP... applicable router config lines: > > ip wccp version 1 > ip wccp web-cache redirect-list 199 > > access-list 199 permit tcp any any eq www > access-list 199 permit tcp any any eq 8080 > > interface FastEthernet3/1 > description connected to EthernetLAN_2 > ip wccp web-cache redirect out > > So it seems like maybe SSL/HTTPS traffic isn't being > forwarded to the squid at all? That is good. Check your firewall logs for traffic from the client and / or to the web server in question. Look for dport 443 to see if that traffic is going out the firewall (i.e. not going thru Squid). > > Sean > > > >>>"Sturgis, Grant" <Grant.Sturgis@xxxxxxxxxxxxxxxxxx> 09/14 12:58 pm > >>> > Let's see what the list says (I have known to be wrong ;-) > > If I am correct, then you cannot intercept SSL requests and > send them to > > your proxy. This technique would be essentially a man-in-the-middle > attack on an SSL connection. > > So, how are you doing transparent proxying / interception? Are you > using WCCP or policy based routing? > > > > > >-----Original Message----- > >From: Listserv [mailto:SALISTSERV@xxxxxxxxxxx] > >Sent: Wednesday, September 14, 2005 10:52 AM > >To: Sturgis, Grant > >Subject: RE: Problem logging in to webmail site > > > > > >>>>"Sturgis, Grant" <Grant.Sturgis@xxxxxxxxxxxxxxxxxx> 09/14 12:38 pm > >>>> > > > > > >>-----Original Message----- > >>From: Listserv [mailto:SALISTSERV@xxxxxxxxxxx] > >>Sent: Wednesday, September 14, 2005 10:31 AM > >>To: squid-users@xxxxxxxxxxxxxxx > >>Subject: Problem logging in to webmail site > >> > >> > >>Hi... I'm fairly new to all this. Inherited a set of squids > >>running transparently for web caching. Everything runs fine, > >>mostly... recently noticed that when I attempt to connect to > >>a certain webmail site, the login box for the site does not > >>pop up... the browser just tries to connect, and connect, and > >>connect. So I set the domain to always connect. This seems > >>to work when I'm connected directly to one of the caching > >>servers, but not when I'm just using the proxy transparently. > >>Any suggestions? > >> > >>This is similar to a login problem that I never got any > >>response on a month or so ago, so any help anyone may have > >>would be greatly appreciated. Thanks! > >> > >>Sean Albright > > > >My guess would be that the login box (frame) is https. Since > >you cannot > > > >transaprently proxy https, the requests are getting lost. You should > >send https requests out directly (not through the proxy). > > > >> > > > >Thanks for the quick response. It's possible that I'm > >already configured to do that... the conf contains the following: > > > >acl SSL_ports port 443 563 > ><snip> > >http_access deny CONNECT !SSL_ports > > > >Is that what you're talking about? > > > >If that's doing something else, how can I send out the > >requests directly... Would I do that something like this: > > > >acl FOO https > >nocache deny FOO > > > > > >Sean > > > > > > This electronic message transmission is a PRIVATE > communication which contains > information which may be confidential or privileged. The > information is intended > to be for the use of the individual or entity named above. If > you are not the > intended recipient, please be aware that any disclosure, > copying, distribution > or use of the contents of this information is prohibited. > Please notify the > sender of the delivery error by replying to this message, or > notify us by > telephone (877-633-2436, ext. 0), and then delete it from > your system. > > This electronic message transmission is a PRIVATE communication which contains information which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender of the delivery error by replying to this message, or notify us by telephone (877-633-2436, ext. 0), and then delete it from your system.
