Re: mod_ext_filter and last-modified header

2004-04-13 Thread Craig Sebenik
Quoting Geoffrey Young ([EMAIL PROTECTED]):
> Craig Sebenik wrote:
> > It looks like mod_ext_filter sets the last-modified http header based on 
> > the mod time of the *filter* file and not the actual file represented by 
> > the URL.
> 
> > the Last-Modified HTTP header seems to be set based on the timestamp on 
> > "/web_home/filters/filter.pl" and NOT on "/web_home/htdocs/file.html"
> 
> I would hope it would be the newer of both, since both contribute to the
> freshness of the content, which is what is important.  if you touch
> file.html do you get the newer timestamp?

my mistake. it looks like it works just the opposite of what i said. if i 
change the *code*, and NOT the file, then the last-modified is unchanged. 
i agree, it should be the newer of both.

(fyi, the machines are in the pacific time zone.)

> ll file.html
-rw-rw-r--   1 craighttp2898 Apr 13 19:03 file.html
> ll ../../public/filters/filter.pl
-rwxrwxr-x   1 craighttp 368 Apr  9 14:39 ../../public/filters/filter.pl*
> HEAD server/form11/file.html
200 OK
Cache-Control: max-age=0, public, must-revalidate
Connection: close
Date: Wed, 14 Apr 2004 02:07:53 GMT
Accept-Ranges: bytes
ETag: "13ec08a-b52-6312b4c0"
Server: Apache/2.0.39 (Unix)
Content-Length: 3178
Content-Type: text/html; charset=ISO-8859-1
Expires: Wed, 14 Apr 2004 02:07:53 GMT
Last-Modified: Wed, 14 Apr 2004 02:03:39 GMT
Client-Date: Wed, 14 Apr 2004 02:04:22 GMT
Client-Response-Num: 1

> touch ../../public/filters/filter.pl
> ll file.html
-rw-rw-r--   1 craighttp2898 Apr 13 19:03 file.html
> ll ../../public/filters/filter.pl
-rwxrwxr-x   1 craighttp 368 Apr 13 19:08 ../../public/filters/filter.pl*
> HEAD server/form11/file.html
200 OK
Cache-Control: max-age=0, public, must-revalidate
Connection: close
Date: Wed, 14 Apr 2004 02:08:28 GMT
Accept-Ranges: bytes
ETag: "13ec08a-b52-6312b4c0"
Server: Apache/2.0.39 (Unix)
Content-Length: 3178
Content-Type: text/html; charset=ISO-8859-1
Expires: Wed, 14 Apr 2004 02:08:28 GMT
Last-Modified: Wed, 14 Apr 2004 02:03:39 GMT
Client-Date: Wed, 14 Apr 2004 02:05:00 GMT
Client-Response-Num: 1


> touch file.html
> ll file.html
-rw-rw-r--   1 craighttp2898 Apr 13 19:15 file.html
> ll ../../public/filters/filter.pl
-rwxrwxr-x   1 craighttp 368 Apr 13 19:08 ../../public/filters/filter.pl*
> HEAD craig-www/form11/file.html
200 OK
Cache-Control: max-age=0, public, must-revalidate
Connection: close
Date: Wed, 14 Apr 2004 02:15:11 GMT
Accept-Ranges: bytes
ETag: "13ec08a-b52-8c057e80"
Server: Apache/2.0.39 (Unix)
Content-Length: 3178
Content-Type: text/html; charset=ISO-8859-1
Expires: Wed, 14 Apr 2004 02:15:11 GMT
Last-Modified: Wed, 14 Apr 2004 02:15:06 GMT
Client-Date: Wed, 14 Apr 2004 02:11:43 GMT
Client-Response-Num: 1


Re: mod_ext_filter and last-modified header

2004-04-13 Thread Geoffrey Young


Craig Sebenik wrote:
> It looks like mod_ext_filter sets the last-modified http header based on 
> the mod time of the *filter* file and not the actual file represented by 
> the URL.

> the Last-Modified HTTP header seems to be set based on the timestamp on 
> "/web_home/filters/filter.pl" and NOT on "/web_home/htdocs/file.html"

I would hope it would be the newer of both, since both contribute to the
freshness of the content, which is what is important.  if you touch
file.html do you get the newer timestamp?

--Geoff


mod_ext_filter and last-modified header

2004-04-13 Thread Craig Sebenik
It looks like mod_ext_filter sets the last-modified http header based on 
the mod time of the *filter* file and not the actual file represented by 
the URL.

eg.

the following filter is configured in httpd.conf

ExtFilterDefine filter-name mode=output intype=text/html outtype=text/html \
cmd="/web_home/filters/filter.pl"

SetOutputFilter filter-name
[etc...]


now, if you try to get the following url:

http://server/file.html

the Last-Modified HTTP header seems to be set based on the timestamp on 
"/web_home/filters/filter.pl" and NOT on "/web_home/htdocs/file.html"

i was hoping that this would be an easy fix for someone a lot more 
familiar with the code.

i do understand that this may change the current behavior of existing apps 
that use mod_ext_filter... so, comments are welcomed...

tia!
craig