Re: [SQU] Port and Error Message Interpretation

A typo on my part.. Why does this NOT match?

----- Original Message -----
From: Karl Jones
To: Squid Users Group
Sent: Thursday, October 26, 2000 2:58 PM
Subject: [SQU] Port and Error Message Interpretation

1) Why is the following '9000' reference matching the port acl? (EXAMPLE A)

2) What exactly does "Service Unavailable" mean (internally, the remote host?)? (EXAMPLE B)

3) I am running ipmon trying to log any activity outbound or inbound through 9000 and I see nothing in the logs from in front of or behind the proxy (using "telnet sitename 9000"). Suggestions?

**EXAMPLE A**

2000/10/26 14:24:53| peerSelect: http://not.really.com/:9000
2000/10/26 14:24:53| cbdataAdd: 120821c
2000/10/26 14:24:53| storeLockObject: key '5FFBF22C0A496A15FA72D744DBA11208' cou
nt=3
2000/10/26 14:24:53| cbdataLock: d3e694
2000/10/26 14:24:53| peerSelectFoo: 'GET not.really.com'
2000/10/26 14:24:53| cbdataAdd: 5e6d24
2000/10/26 14:24:53| cbdataLock: 541e90
2000/10/26 14:24:53| cbdataLock: 120821c
2000/10/26 14:24:53| cbdataValid: 541e90
2000/10/26 14:24:53| aclCheck: checking 'always_direct allow special'
2000/10/26 14:24:53| aclMatchAclList: checking special
2000/10/26 14:24:53| aclMatchAcl: checking 'acl special port 9000'
2000/10/26 14:24:53| aclMatchAclList: returning 0
 
**EXAMPLE B**

2000/10/26 14:24:53| fwdFail: ERR_CONNECT_FAIL "Service Unavailable"
        http://not.really.com/:9000

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html