RE: Minor Problems

On Fri, 24 Mar 2000, Duwayne Engelhardt wrote:

> System: Linux- Mandrake (MacMillan Edition); Squid 2.2 Stable 4; ACL lists
> set for internal network only; Firewalling with IP Chains with no outside
> access to inside, but all from inside to outside. (This could be the problem
> if the outside web site is attempting to insert a cookie). When a form is
> completed and the Submit or Continue button is clicked, the submission is
> timed out on the outside server. Question is: Why does the submission of
> the form page time out? Is there a way to allow it to occur through the
> Squid proxy, and how do I do that?

Maybe you have the same bug as described here:

http://www.squid-cache.org/Versions/v2/2.2/bugs/#squid-2.2.stable4-pconn-msie-win31-post

        When the client side is using Windows 3.11 with Microsoft's
        TCP/IP-32 v3.11a and Internet Explorer 4.0 or later, the user
        can not send mail (send and store). All he gets is a white
        screen (empty frame), no mail is being sent, no mail is being
        stored in the 'out' folder. We did communication traces and
        found that the proxy server is sending TCP RESET packets to the
        client, but the client still sends data on the same connection,
        in violation of the TCP protocol. Netscape seems to somehow
        realize the data could not be transferred and opens new
        connections, resending the data. MSIE does not do this. NT is
        only sending one single request per connection. TCP/IP protocol
        violation and problems only with HTTP 1.1 browsers. Slowly this
        rang a bell. I guessed that if the proxy could forbid
        persistent connections, the problem would go away.

If so, you could probably fix it by upgrading to squid 2.3.STABLE2 and
disabling persistent connections with

    client_persistent_connections off
    server_persistent_connections off
Received on Fri Mar 24 2000 - 08:38:23 MST