On 07/01/02(01:14) you "Marc Pohl" <firstname.lastname@example.org> wrote
|But this happens only with http/1.0 keep-alive. If the IE 5.5-Setting "Use
|HTTP/1.1 for Proxy-Connections" is activated, all works as desired. If i
|change the Cache-Behaviour of IE, so that the 304-requests don't happen,
|there is also no problem ...
The difference between behaviors of DeleGate for HTTP/1.0 Keep-Alive
and HTTP/1.1 is that, only in former case DeleGate does buffering
of response message to make sure the length of response message
to be put into the Content-Length header, to ensure the functionality
of Keep-Alive mechanism in HTTP/1.0, which is not necessary in HTTP/1.1
because of its "chunked" encoding.
In HTTP/1.0 Keep-Alive, a buffered message is flushed toward the client
in HTTP_putMIMEmsg(). A possible scenario to explain your situation
is that flushHead()->fflush() called from the function returns EOF
by some reason after flushed the header, thus aborting relay of body.
In this case, you see "## stop relay-3: flush()=EOF, client seems dead"
in the LOGFILE. I wish if I could see the LOGFILE.
@ @ Yutaka Sato <email@example.com> http://www.delegate.org/y.sato/
( - ) National Institute of Advanced Industrial Science and Technology (AIST)
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan