www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: mod_dir/3596: mod_dir doesn't handle requests which must be processed internally by mod_proxy
Date Wed, 21 Apr 1999 17:30:01 GMT
The following reply was made to PR mod_dir/3596; it has been noted by GNATS.

From: Dean Gaudet <dgaudet@arctic.org>
To: Radu Greab <radu@netsoft.ro>
Cc: apbugs@apache.org
Subject: Re: mod_dir/3596: mod_dir doesn't handle requests which must be processed internally
by mod_proxy
Date: Wed, 21 Apr 1999 10:20:45 -0700 (PDT)

 On Wed, 21 Apr 1999, Radu Greab wrote:
 
 > dgaudet@apache.org writes:
 >  > No, you have to fill in r->finfo if you're implementing
 >  > something which pretends to be the filesystem... that's
 >  > just how it is.  You don't have to fill in much, just
 >  > set the mode and mtime or something like that.  I know,
 >  > it's not well documented, but what of the api is?
 > 
 > Do you suggest that just because I need to transparrently provide
 > dynamic content from another server I have to create bogus files on
 > the filesystem?
 
 No I wasn't saying that.  I'm saying if a content handler provides
 file-like objects it needs to fill in r->finfo.st_mode and
 r->finfo.st_mtime.  It doesn't need to create files to do that.
 
 > To solve my problem I have a few possibilities:
 > 1) use my patch against mod_dir to make it proxy aware. The advantage
 > is that I can use a minimum configuration in httpd.conf (one line) and
 > it doesn't require _bogus_ files and the task can be solved with two
 > modules compiled in: mod_dir and mod_proxy.
 
 The bug isn't in mod_dir, it's in mod_proxy.  mod_dir follows the API.
 
 Dean
 

Mime
View raw message