You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by David Wheeler <da...@wheeler.net> on 2002/07/05 22:25:44 UTC
Apache->print Timed Out
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 mod_ssl/2.8.9 OpenSSL/0.9.6b
This is on RedHat Linux 7.2.
I did a quick google search, but found no obvious answers to this issue.
Anyone got any ideas what could be happening? Why and under what
circumstances will Apache->print time out?
TIA,
David
--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Re: $r->path_info question
Posted by darren chamberlain <dl...@users.sourceforge.net>.
* simran <si...@cse.unsw.edu.au> [2002-07-23 05:11]:
> However: if i create an 'auto' directory in my document root
> (something that was not there before)
>
[-- snip --]
> Is this is feature or a bug, does path_info not check the 'Location' it
> matced the handler to or is it meant to look at the directory structure?
This is how Apache handles path_info: it is the "extra" stuff after
the translation handler has found a directory and filename. It starts
at the left, and walks towards the right, until it finds the last
component that is a directory, and then the next piece is the file (no
existance check is done at this point). The rest of it is path_info.
For example:
A request for /foo/bar/baz/quux, with a document root of /document/root
(assuming no Alias directives, that complicates things slightly), and
assuming that /document/root/foo is the last *directory* in the path
that exists, Apache does this:
1. look for /document -> yep
2. look for /document/root -> yep
3. look for /document/root/foo -> yep
4. look for /document/root/foo/bar -> nope
So /document/root/foo/bar is r->filename, and /baz/quux is path_info.
To reiterate: this is not a mod_perl thing (bug/whatever) but an Apache
one.
(darren)
--
An operating system is just a name you give the features you left
out of your editor.
-- Per Abrahamsen in comp.emacs
$r->path_info question
Posted by simran <si...@cse.unsw.edu.au>.
Hi All,
If i use hte following configuration:
apache.conf
============
<Location /auto/thumbnails>
SetHandler perl-script
PerlHandler My::Thumbnails
</Location>
Then in my handler sub in Thumbnails.pm do:
==========================================
my $r = instance Apache::Reuest(shift);
print STDERR "PathInfo: "$r->path_info()."\n";
Then i go to the url:
======================
http://localhost/auto/thumbnails/images/a.gif
In my error log i get
======================
PathInfo: /thumbnails/images/a.gif
However: if i create an 'auto' directory in my document root (something
that was not there before)
i get:
PathInfo: /images/a.gif
(which i like :-)
Is this is feature or a bug, does path_info not check the 'Location' it
matced the handler to or is it meant to look at the directory structure?
simran.
Re: Apache->print Timed Out
Posted by David Wheeler <da...@wheeler.net>.
On 7/21/02 8:19 AM, "Ask Bjoern Hansen" <as...@develooper.com> 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 AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Re: Apache->print Timed Out
Posted by Ask Bjoern Hansen <as...@develooper.com>.
On Sat, 20 Jul 2002, David Wheeler wrote:
[...]
> we've been running Bricolage on them for some time. Something must have
> changed in our HTML or something to suddenly trigger these dodgy clients to
> start dropping the connection. Curiously, it seems to happen only for large
> pages -- over 31K or so.
[...]
> > Probably buggy browsers or TCP stacks.
>
> Yeah, that's my guess, too. But, like I said, we must have changed something
> to suddenly start triggering it. It can't really be the size of the files
> sent, as others would have noticed it on other large pages ages ago.
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].
- ask
[1] Sometimes I use MSIE on Mac OS X and about once a month or so I
encounter a webpage that'll make it crash.
--
ask bjoern hansen, http://askbjoernhansen.com/ !try; do();
Re: Apache->print Timed Out
Posted by David Wheeler <da...@wheeler.net>.
On 7/18/02 7:10 PM, "Perrin Harkins" <pe...@elem.com> claimed:
Hi Perrin, thanks for your response.
> 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 forwarded your message to the Bricolage list, and the guy experiencing the
problem (Win 95/Netscape 4.79) claimed that it made no difference. It seems
strange that these clients would start dropping the connection now, after
we've been running Bricolage on them for some time. Something must have
changed in our HTML or something to suddenly trigger these dodgy clients to
start dropping the connection. Curiously, it seems to happen only for large
pages -- over 31K or so.
> This isn't the same thing as CORE::print. It's overriden for mod_perl
> to send to the network. Even CORE::print can return false in certain
> conditions, like when writing a file when the disk is full.
Yeah, I knew it wasn't CORE::print, but I hadn't thought about the network
dependency. It would make sense that Apache->print would time out if the
browser it was essentially printing to over the network stopped listening.
>> And why does it only happen for some
>> browser/platform combinations?
>
> Probably buggy browsers or TCP stacks.
Yeah, that's my guess, too. But, like I said, we must have changed something
to suddenly start triggering it. It can't really be the size of the files
sent, as others would have noticed it on other large pages ages ago.
I'm not sure how to go about trying to fix this, unfortunately...
Thanks!
David
--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Re: Apache->print Timed Out
Posted by Perrin Harkins <pe...@elem.com>.
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 timing out was
> something that a print method could do.
This isn't the same thing as CORE::print. It's overriden for mod_perl
to send to the network. Even CORE::print can return false in certain
conditions, like when writing a file when the disk is full.
> And why does it only happen for some
> browser/platform combinations?
Probably buggy browsers or TCP stacks.
- Perrin
Re: Apache->print Timed Out
Posted by David Wheeler <da...@wheeler.net>.
On 7/10/02 10:37 AM, "David Wheeler" <da...@wheeler.net> claimed:
> I have a couple of strange bugs showing up in Bricolage that have something
> to do with Apache->print timing out (with Win 95 and Mac OS 9 -- yes, these
> folks need to join the new millennium), and have no idea how or under what
> circumstances print times out.
Okay, I've got the output of some tcpdump runs in Bricolage Bugzilla.
http://bricolage-bugzilla.thepirtgroup.com/showattachment.cgi?attach_id=35
All they demonstrate, however, is that Apache/mod_perl never finishes
sending the page to the browser. One page is 32120 bytes, and the other is
36500 bytes. I really have no clue what could be causing this. Why should
Apache->print ever time out? I didn't even know that timing out was
something that a print method could do. And why does it only happen for some
browser/platform combinations?
Anyone who has some ideas, or who can suggest other approaches to diagnosing
the problem, will get a great deal of gratitude from me and many Bricolage
users.
Thanks,
David
--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org
Re: Apache->print Timed Out
Posted by David Wheeler <da...@wheeler.net>.
I think I made a mistake posting this query over the holiday weekend, so I'm
gonna speak up again.
I have a couple of strange bugs showing up in Bricolage that have something
to do with Apache->print timing out (with Win 95 and Mac OS 9 -- yes, these
folks need to join the new millennium), and have no idea how or under what
circumstances print times out.
Any enlightenment on this issue would be most welcome.
Thanks!
David
On 7/5/02 1:25 PM, "David Wheeler" <da...@wheeler.net> claimed:
> 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 mod_ssl/2.8.9 OpenSSL/0.9.6b
>
> This is on RedHat Linux 7.2.
>
> I did a quick google search, but found no obvious answers to this issue.
> Anyone got any ideas what could be happening? Why and under what
> circumstances will Apache->print time out?
>
> TIA,
>
> David
--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory@jabber.org