>
>
> Very open to discuss this one, I have some doubts too. I chose to drop the
> header since I applied 14.29 only to dates (i.e. not triggering any
> APR_DATE_BAD after parsing) and not to completely wrong values like "foo".
> My aim was to drop any non parsable date (logging
y
APR_DATE_BAD after parsing) and not to completely wrong values like "foo".
My aim was to drop any non parsable date (logging the action) and to
correct the rest if considered in the future from httpd's point of view.
>
>
>> 2) Last-Modified header value with a dat
now(), based on comments in
14.29?
> 2) Last-Modified header value with a date not in GMT are replaced with
> (now() + time taken to serve the request) without any trace in the logs.
> This seems to be due to httpd recognizing the date as "in the future" and
> replacing i
simple PHP script forces httpd to
replace it with Thu, 01 Jan 1970 00:00:00 GMT. Patch proposed to backport:
http://svn.apache.org/r1748379
2) Last-Modified header value with a date not in GMT are replaced with
(now() + time taken to serve the request) without any trace in the logs.
This seems to
> wrote:
>>>>>
>>>>>> On Mon, Jun 6, 2016 at 4:09 PM, Luca Toscano
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> I was able to repro building httpd from 2.4.x branch and following
>>>>>>
>>>
>>>>>>
>>>>>> I was able to repro building httpd from 2.4.x branch and following
>>>>>> your configuration files on github. I am almost sure that somewhere httpd
>>>>>> sets the Last-Modified header translating "
, Vacelet, Manuel <
>>> manuel.vace...@enalean.com> wrote:
>>>
>>>> On Mon, Jun 6, 2016 at 4:09 PM, Luca Toscano
>>>> wrote:
>>>>
>>>>>
>>>>> I was able to repro building httpd from 2.4.x branch and following
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 t
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 N
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
Jie Gao wrote:
>>This is quite ambiguous, but I think this is how it should read:
>>
>>On the Apache web server, the last modified HTTP header is returned if
>>the file is an HTML file. If it is a SHTML (or processed by
>>mod_include), then the last modified head
eturned if
> the file is an HTML file. If it is a SHTML (or processed by
> mod_include), then the last modified header is only returned when
> the SHTML file is executable. Otherwise, for a SHTML file with no
> executable bit set, no last modified information is returned.
Thanks.
What wo
gt; permission, then no last modified information is returned.
This is quite ambiguous, but I think this is how it should read:
On the Apache web server, the last modified HTTP header is returned if
the file is an HTML file. If it is a SHTML (or processed by
mod_include), then the last
sion, then no last modified information is returned.
>
> If this is still the case, it is impossible to take advantage of
> Solaris' priority_paging if "last modified" header is also wanted.
Why do you want priority paging on HTML/SHTML files?
-aaron
ase, it is impossible to take advantage of
Solaris' priority_paging if "last modified" header is also wanted.
Can this be changed to send "last modified" header everytime?
> All priority paging does is set a new kernel parameter, cachefree, to
> twice the value of
it, and it should be disabled. (Of course, I have not
> really checked to see that nothing else will break.)
OK, in any case, can we opt out the perl.apache.org from automatically
using mod_include
if it's not possible to change mod_inclu
On Mon, 15 Apr 2002, Stas Bekman wrote:
> Which makes all ASF projects sites running of daedalus cache
> non-friendly. Is this good?
No. Only httpd.apache.org actually uses includes as far as I know. Other
sites don't need it, and it should be disabled. (Of course, I have not
really checked t
Justin Erenkrantz wrote:
> On Mon, Apr 15, 2002 at 11:59:00AM +0800, Stas Bekman wrote:
>
>>2.0.35 or whatever version is running on apache.org at this moment
>>doesn't set the Last-Modified header for static pages requests.
>
>
> Daedalus won't because
On Mon, Apr 15, 2002 at 11:59:00AM +0800, Stas Bekman wrote:
> 2.0.35 or whatever version is running on apache.org at this moment
> doesn't set the Last-Modified header for static pages requests.
Daedalus won't because everything is run through mod_include.
It&#
2.0.35 or whatever version is running on apache.org at this moment
doesn't set the Last-Modified header for static pages requests.
% HEAD http://httpd.apache.org/index.html
200 OK
Connection: close
Date: Mon, 15 Apr 2002 03:57:38 GMT
Accept-Ranges: bytes
Server: Apache/2.0.35 (Unix)
Co
20 matches
Mail list logo
