I get a lot of lines that say: 1073682097.533 2 64.171.70.171 TCP_DENIED/407 1755 CONNECT 38.118.153.126:443 - NONE/- text/html
along with: 1073682097.561 63 64.171.70.171 TCP_MISS/200 164 POST http://38.118.153.221/idle/142032232/306 austin DIRECT/38.118.153.221 - or 1073682097.496 2 64.171.70.171 TCP_DENIED/407 1821 POST http://38.118.153.221/idle/142032232/306 - NONE/- text/html every once in a while. I guess this means that squid is blocking 443 then (but still letting the connection through for a split second?) I looked at the config file, and I found 443 listed in SSL_ports and Safe_ports, but I didn't see anything about having it denied. ----- Original Message ----- From: "Henrik Nordstrom" <[EMAIL PROTECTED]> To: "Austin Lee" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, January 13, 2004 1:58 AM Subject: Re: [squid-users] Squid and Flash Comm Server MX 1.5 > On Mon, 12 Jan 2004, Austin Lee wrote: > > > Our company has a Flash Communications Server MX 1.5 application. When I connect > > to it through squid, it keeps on generating connections until the server limit > > is reached. Why does it do this? The connection from the workstation to squid > > shows that there are only two connections (and the ids do not change), and when > > I don't go through squid, there are only two connections directly to the Flash > > server. > > What does access.log say? > > See also http://www.squid-cache.org/Versions/V2/2.5/bugs/ > > Regards > Henrik > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.557 / Virus Database: 349 - Release Date: 12/30/2003
