You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "Ahn, Chang" <ah...@staff.abanet.org> on 2006/06/22 21:12:04 UTC
[users@httpd] How to enable modification date for SSI files
I'm using SSI for most of my site and just noticed that the response
header isn't sending the file's last modified date. In Apache
configuration, can you configure Apache to send the requested SSI file's
last modified date in the HTTP header without resorting to XBitHack or
code modification?
I know I can use XBitHack full; however, I have to turn the group
execute bit on (which my security office won't like). And because of
the way our CMS is setup, it's difficult to discriminately turn on the
execute bit for specific file types. And I rather not have to add SSI
code into each file, but that would be a very extensive code
modification (we have several thousand files).
I've read the mod_expires may offer a method. I've gotten it to work...
sort of.
This works, but it uses access time as the modified date.
<IfModule mod_expires.c>
ExpiresActive on
ExpiresDefault "access plus 1 days"
</IfModule>
When I change to modification, it still returns the access time as the
modified date. Am I going down the wrong path or is this configuration
wrong?
<IfModule mod_expires.c>
ExpiresActive on
ExpiresDefault "modification plus 1 days"
</IfModule>
I may have to use XBitHack but I want to investigate possible
alternatives first.
Re: [users@httpd] How to enable modification date for SSI files
Posted by Joshua Slive <jo...@slive.ca>.
On 6/22/06, Ahn, Chang <ah...@staff.abanet.org> wrote:
> I'm using SSI for most of my site and just noticed that the response header
> isn't sending the file's last modified date. In Apache configuration, can
> you configure Apache to send the requested SSI file's last modified date in
> the HTTP header without resorting to XBitHack or code modification?
No, I don't believe so.
> I've read the mod_expires may offer a method. I've gotten it to work... sort
> of.
>
> This works, but it uses access time as the modified date.
> <IfModule mod_expires.c>
> ExpiresActive on
> ExpiresDefault "access plus 1 days"
> </IfModule>
>
> When I change to modification, it still returns the access time as the
> modified date. Am I going down the wrong path or is this configuration
> wrong?
>
> <IfModule mod_expires.c>
> ExpiresActive on
> ExpiresDefault "modification plus 1 days"
> </IfModule>
Neither of these set the Last-Modified header. They both set the
Expires and Cache-Control: max-age header.
Also note that the mod_expires docs say:
"Note that if you use a modification date based setting, the Expires
header will not be added to content that does not come from a file on
disk. This is due to the fact that there is no modification time for
such content."
This probably applies to mod_include generated files.
Finally, don't include the <IfModule ...> and </IfModule> lines.
These just serve to obscure useful error messages.
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org