[SQU] ssl sides connecting problem

From: Ilker Gokhan <IlkerG@dont-contact.us>
Date: Wed, 6 Sep 2000 16:07:03 +0300

Hi,

I have three squid servers (2.3ST1 no patch) on the different side. im
getting error from only one (im not getting from others) while want to
connect fortify.net to check supported SSL version of the browsers. I have
compared the squids configuration but i couldnt find any different
configuration option between them.

Unfortunately, the same connect problem is including whole ssl sides. For
instance:
967722286.674 120420 10.0.16.108 TCP_MISS/000 0 CONNECT
sube.etibank.com.tr:443 - DIRECT/sube.etibank.com.tr -
967722407.204 119528 10.0.16.108 TCP_MISS/000 0 CONNECT
sube.etibank.com.tr:443 - DIRECT/sube.etibank.com.tr -
^^

According to me, cache.log says there isnt any problem:
2000/09/01 17:58:52| httpRequestFree: al.url='www.fortify.net:443'
2000/09/01 17:58:52| fd_close FD 10 www.fortify.net:443
2000/09/01 17:58:52| destroying entry 0x8215b00: 'Host: www.fortify.net'
2000/09/01 17:58:52| fd_close FD 13 www.fortify.net:443
2000/09/01 17:59:47| parseHttpRequest: URI is 'www.fortify.net:443'
Host: www.fortify.net
Host: www.fortify.net
Host: www.fortify.net
2000/09/01 17:59:47| creating entry 0x971b020: near 'Host: www.fortify.net'
2000/09/01 17:59:47| created entry 0x971b020: 'Host: www.fortify.net'
2000/09/01 17:59:47| The request CONNECT www.fortify.net:443 is ALLOWED,
because
 it matched 'laneti'
2000/09/01 17:59:47| redirectStart: 'www.fortify.net:443'
2000/09/01 17:59:47| clientRedirectDone: 'www.fortify.net:443' result=NULL
2000/09/01 17:59:47| clientProcessRequest: CONNECT 'www.fortify.net:443'
2000/09/01 17:59:47| sslStart: 'CONNECT www.fortify.net:443'
2000/09/01 17:59:47| fd_open FD 11 www.fortify.net:443
2000/09/01 17:59:47| peerSelectFoo: 'CONNECT www.fortify.net'
2000/09/01 17:59:47| peerGetSomeParent: CONNECT www.fortify.net
2000/09/01 17:59:47| commConnectStart: FD 11, www.fortify.net:443
2000/09/01 17:59:47| ipcache_nbgethostbyname: Name 'www.fortify.net'.
2000/09/01 17:59:47| ipcache_nbgethostbyname: HIT for 'www.fortify.net'
2000/09/01 17:59:47| ipcache_nbgethostbyname: HIT for 'www.fortify.net'
2000/09/01 17:59:47| ipcacheCycleAddr: www.fortify.net now at 209.207.221.16
2000/09/01 18:01:04| parseHttpRequest: URI is 'http://www.fortify.net/'
Host: www.fortify.net
Host: www.fortify.net
Host: www.fortify.net
2000/09/01 18:01:04| creating entry 0x8207950: near 'Host: www.fortify.net'
2000/09/01 18:01:04| created entry 0x8207950: 'Host: www.fortify.net'
2000/09/01 18:01:04| The request GET http://www.fortify.net/ is ALLOWED,
because
 it matched 'laneti'
2000/09/01 18:01:04| redirectStart: 'http://www.fortify.net/'
2000/09/01 18:01:04| clientRedirectDone: 'http://www.fortify.net/'
result=NULL
2000/09/01 18:01:04| clientProcessRequest: GET 'http://www.fortify.net/'
2000/09/01 18:01:04| clientProcessRequest: TCP_HIT for
'http://www.fortify.net/'
2000/09/01 18:01:04| clientCacheHit: http://www.fortify.net/, 1266 bytes
2000/09/01 18:01:04| refreshCheck(HTTP): 'http://www.fortify.net/'
2000/09/01 18:01:04| modifiedSince: 'http://www.fortify.net/'
2000/09/01 18:01:04| storeCreateEntry: 'http://www.fortify.net/'
2000/09/01 18:01:04| storeKeyPrivate: GET http://www.fortify.net/
2000/09/01 18:01:04| clientSendMoreData: http://www.fortify.net/, 137 bytes
2000/09/01 18:01:04| clientSendMoreData: FD 12 'http://www.fortify.net/',
out.of
fset=0
2000/09/01 18:01:04| storeSwapOut: http://www.fortify.net/

access.log:
967722286.674 120420 10.0.16.108 TCP_MISS/000 0 CONNECT www.fortify.net:443
- DIRECT/fortify.net -
967722407.204 119528 10.0.16.108 TCP_MISS/000 0 CONNECT www.fortify.net:443
- DIRECT/fortify.net -
^^

Any help would be appreciated ...

Greetings,
Ilker G.

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
Received on Wed Sep 06 2000 - 07:07:40 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:55:12 MST