Hi *;
Kristian Rink schrieb:
[...]
> SetEnv force-proxy-request-1.0 1
> SetEnv proxy-nokeepalive 1
> SetEnv proxy-sendchunked 1
[...]
... neverending story, ClientAbortException and different browsers. Some
more experiences on that very problem I managed to collect:
- I am using apache2 mod_setenvif with a configuration like that:
BrowserMatch "MSIE 6\." nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "MSIE 7\." nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "MSIE 5\." nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "MSIE 4\." nokeepalive downgrade-1.0 force-response-1.0
- This way, for the first time I was actually capable to reproduce the error
on one of my machines: Toggling the above line for MSIE 7 off reliably made
our testbed browser end up with a "page not found or server not responding"
error message whenever accessing one of the download resources. Needless to
say I left it activated, yet there still are some of these errors once in a
while, though it has generally calmed down pretty much.
- I added some more logging to the code in order to see what happens there -
in some situations indeed the exception seems to be thrown after everything
happened, but it seems the majority of these exceptions happened after
exactly 262144 bytes have been sent down the line. Can anyone quickly
remember where in HTTP specification 256 kB might be a magical number?
Still working on this;
Kristian
--
Kristian Rink
cell : +49 176 2447 2771
business: http://www.planconnect.de
personal: http://pictorial.zimmer428.net
"we command the system. calling all recievers.
we are noisy people for a better living".
(covenant - "monochrome")