austinhere wrote:
1246076496.527 79 (ip_hidden) TCP_MISS/200 4467 CONNECT
login.yahoo.com:443 - DIRECT/209.191.92.114 -
1246076496.689 139 (ip_hidden) TCP_MISS/302 1451 GET
http://us.f1119.mail.yahoo.com/ym/login? - DIRECT/98.137.26.66 text/html
1246076496.730 38 (ip_hidden) TCP_MISS/302 564 GET
http://login.yahoo.com/config/mail? - DIRECT/209.191.92.114 text/html
1246076496.828 94 (ip_hidden) TCP_MISS/200 10754 CONNECT
login.yahoo.com:443 - DIRECT/209.191.92.114 -
1246076496.949 42 (ip_hidden) TCP_MISS/200 3005 CONNECT
us.bc.yahoo.com:443 - DIRECT/68.142.213.159 -
trying to get Squid working with Yahoo webmail (and some others that arent
working)
...i can use gmail and even services like Meebo without an issue but things
like my Yahoo and my GoDaddy webmail seem to authenticate
(if i use wrong credentials it tells me so) but then doesnt actually log
in... just tosses me back to the login
GET POST CONNECT methods all allowed.... not caching...
I am running a multiple IP setup using this:
http_port x.x.x.246:3129
http_port x.x.x.247:3130
http_port x.x.x.248:3131
http_port x.x.x.249:3132
http_port x.x.x.250:3133
acl example_dst1 myip x.x.x.246
acl example_dst2 myip x.x.x.247
acl example_dst3 myip x.x.x.248
acl example_dst4 myip x.x.x.249
acl example_dst5 myip x.x.x.250
tcp_outgoing_address x.x.x.246 example_dst1
tcp_outgoing_address x.x.x.247 example_dst2
tcp_outgoing_address x.x.x.248 example_dst3
tcp_outgoing_address x.x.x.249 example_dst4
tcp_outgoing_address x.x.x.250 example_dst5
Tried this... no change:
acl url dstdomain .yahoo.com
always_direct allow url
prevents a cache_peer being used to forward traffic. You don't seem to
have any so forcing always_direct is not worthwhile.
cache deny url
Any ideas?
The trace you provided show several requests going through from your
client to various yahoo domains and not having any problems at all.
The problem is either with the data inside the requests/replies being
passed around or in some transaction you omit from the above trace (it
happens sometimes that a second security check gets done on strange
domains).
We can't tell whats going wrong from the given info. Perhapse the HTTP
headers involved may help. And an indication whether the browser is
configured to use the proxy or if its intercepted.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16
Current Beta Squid 3.1.0.9
