On 7/21/02 8:19 AM, Ask Bjoern Hansen [EMAIL PROTECTED] claimed:
You didn't tell which version of MSIE they use; but if it's not
recent it could be some CSS that makes the browser act up[1].
V.5, I think. It doesn't happen on OS X, though, only OS 9.
David
--
David Wheeler
This may be a long shot but the circumstances sound familiar. I had a problem
where an HTTP connection was simply not being properly closed and Netscape4
was just hanging around waiting for the response to finish whereas other
browsers/platforms had no problem, ie. the other browsers were
David Wheeler wrote:
Why should Apache-print ever time out?
One reason could be a web client that disconnects. There could also be
a dropped network connection or one that's too slow. I think you can
adjust this behavior with the TimeOut directive in httpd.conf.
I didn't even know that
loaded and I'm seeing this message in the log error log:
[Fri Jul 5 20:22:17 2002] [info] [client 192.168.1.1] mod_perl:
Apache-print timed out
Config:
Apache/1.3.26 (Unix) mod_perl/1.27 mod_ssl/2.8.9 OpenSSL/0.9.6b
This is on RedHat Linux 7.2.
I did a quick google search
Hi All,
I'm seeing some strange behavior with IE/Mac OS Classic where pages aren't
getting completely loaded and I'm seeing this message in the log error log:
[Fri Jul 5 20:22:17 2002] [info] [client 192.168.1.1] mod_perl:
Apache-print timed out
Config:
Apache/1.3.26 (Unix) mod_perl/1.27
