On 3/15/06, Henrik Nordstrom <henrik@xxxxxxxxxxxxxxxxxxx> wrote: > ons 2006-03-15 klockan 10:09 +0100 skrev Frans Haarman: > > Are you sure it's the SSL session setup taking long and not something in > the returned page getting the browser confused? > > Try fetching just the HTML with wget, and verify that all returned links > etc are correct... I am now using Squid3 to be OWA frontend with the front-end-https. Works great. However I wonder if someone on this list managed to get RPC over HTTPS working using squid3 ?? Seems al connections from outlook stop at my squid3. I did some testing with the slow SSL sessions. This is a tcpdump of the https session. 0.771862 172.16.11.175 -> 172.16.10.83 SSLv3 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message 0.775782 172.16.10.83 -> 172.16.11.175 SSLv3 Change Cipher Spec, Encrypted Handshake Message 0.909138 172.16.11.175 -> 172.16.10.83 TCP 2290 > 443 [ACK] Seq=283 Ack=1200 Win=64321 Len=0 1.120477 208.174.60.61 -> 172.16.11.175 TCP 80 > 2291 [RST, ACK] Seq=0 Ack=0 Win=64512 Len=0 4.870862 208.174.60.61 -> 172.16.11.175 TCP 80 > 2291 [RST, ACK] Seq=0 Ack=0 Win=64512 Len=0 10.147979 172.16.11.175 -> 172.16.10.83 TCP 2290 > 443 [FIN, ACK] Seq=283 Ack=1200 Win=64321 Len=0 10.148792 172.16.10.83 -> 172.16.11.175 TCP 443 > 2290 [ACK] Seq=1200 Ack=284 Win=65535 Len=0 10.149696 172.16.10.83 -> 172.16.11.175 SSLv3 Encrypted Alert Somehow there are 2 connection from an IP I do not know (208.x ). After this weirdness everything works fine. So its probably not a squid issue.... anybody have a clue what is going on ? I'd rather find out what this is. I am sure more people might encounter this. Regards, Frans
