> [karl - Mon Aug 01 17:45:21 2011]: > > In case it isn't clear: ttn doesn't want to use SSI, and his real pages > don't use it. The only reason he was experimenting with it was because > I found that http-equiv as an alternative to server configuration > changes. So the question is whether Last-Modified: can be turned on for > non-SSI pages.
You can't tell whether or not a page uses SSI before parsing it, and parsing happens after the server has sent the HTTP headers. Wildebeest is configure to process all .html and .shtml pages with SSI. Changing it to process only the .shtml extension is unfeasible, because we'd have to rename a large number of pages across several repositories. See also my comments in the Savannah ticket. > (It seems bizarre to me that Apache's syntax for the SSI version of > Last-Modified: would be different from the normal-header version, so I'm > not sure it's going to solve his w3m problem anyway, but I suppose > anything's possible.) That's because the SSI command is not meant to be used for generating HTTP headers. It's usually expanded in the footer of pages. -- Bernie Innocenti Systems Administrator, Free Software Foundation
