Opened 16 years ago
Closed 14 years ago
#8525 closed (wontfix)
Generic views should automatically set Last-Modified header
| Reported by: | matehat | Owned by: | nobody |
|---|---|---|---|
| Component: | Generic views | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Wouldn't it be nice, since generic views often generate content based on querysets, if these views could also automatically set the "Last-Modified" HTTP header on the response object? The ConditionalGet middleware could then produce "Not Modified" responses when it should, and we could save some bandwidth.
Change History (2)
comment:1 by , 16 years ago
| Summary: | Last-Modified Header automatically set by generic views → Generic views should automatically set Last-Modified header |
|---|---|
| Triage Stage: | Unreviewed → Design decision needed |
comment:2 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
While this is a nice idea, without a concrete suggestion of how last-modified can be calculated in the generic sense, I'm closing wontfix.
Note:
See TracTickets
for help on using tickets.
How would the generic view know the last-modified date?