Re: [squid-users] trouble with POST and squid-2.4.STABLE6

"Conection: close" should not make any difference. The meaning in
HTTP/1.0 is the same as if it isn't there as HTTP/1.0 always closes
the connection unless indicated otherwise in the
Connection/Proxy-Connection headers..

But maybe there is problems with keeping the connection alive. Start
by testing

  client_side_persistent_connections off

and if that does not help

  server_side_persistent_connections off

And report to squid-bugs@squid-cache.org if any of the directives
helped.

Regards
Henrik

On Thursday 13 June 2002 03:14, Eric D. Hendrickson wrote:
> I'm back to looking at this problem again and I may have found a
> clue. I think I need to find out how to disable squid from adding
> a "Connection: close" header. How do I do that?
>
> > > 1022705954.849 142 <my.ip> TCP_MISS/200 5601 GET
> > > http://<external.FQDN>/pgLogin.html -
> > > DIRECT/<ip.of.external.FQDN> text/html 1022705973.164 11445
> > > <my.ip> TCP_MISS/200 357 POST
> > > http://<external.FQDN>/pgLogin.html -
> > > DIRECT/<ip.of.external.FQDN> text/html
> > >
> > > Can anyone give me some pointers on what I am missing to make
> > > this work?
> >
> > As far as the above log, it seems it actually did work... You got
> > pgLogin.html, posted some data there and got a successful reply
> > back.
Received on Thu Jun 13 2002 - 03:15:40 MDT