MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#640 — Ability to define HTTP headers for a site and documents
Attached to Project —
MODx
Opened by Grzegorz Adamiak (grad) - Friday, 03 November 2006, 04:29AM
Last edited by Ryan Thrash (rthrash) - Wednesday, 08 November 2006, 11:29AM
Opened by Grzegorz Adamiak (grad) - Friday, 03 November 2006, 04:29AM
Last edited by Ryan Thrash (rthrash) - Wednesday, 08 November 2006, 11:29AM
| Task Type | ToDo |
|---|---|
| Category | Core Distribution |
| Status | New |
| Assigned To | No-one |
| Operating System | All |
| Severity | Medium |
|---|---|
| Priority | Normal |
| Reported Version | 0.9.5 beta5 |
| Due in Version | 0.9.7 |
| Due Date | Undecided |
| Percent Complete |
|
Details
Rev. 1902It would be useful to be able to define some of the HTTP headers for a site (global settings) and for single document (override of a global setting). The headers available for setting should include:
* Expires
* Cache-Control
* Pragma
This task depends upon
This task blocks these from closing
While in standard conditions, Last-Modified header should be based on the last modification date of a document, in some cases it would be usful to be able to set it to a time offset.
In particular fully automatic document listings (when the containing document is not being modified itself) or feeds would benefit from setting the Last-Modified header to, say, 1 day (or 1 hour) ago. Another way to resolve this would be to use the modification date of the newest content part. But this would require another FR.