Ticket #2050 (new defect)

Opened 10 years ago

Last modified 9 years ago

Portal-wide support for 304 responses

Reported by: gracinet Owned by: trac
Priority: P2 Milestone: CPS 3.5.7
Component: CPSDefault Version: TRUNK
Severity: normal Keywords:


I have code in a personal project improving the HTTP caching capabilities by issuing proper 304 (Not modified) responses. This works with a conflict-free global last modification date. In turn this very same project would benefit a cleaner integration from the new void response handling system of #2040.

Change History

comment:1 Changed 10 years ago by gracinet

  • Milestone changed from CPS 3.5.0 to CPS 3.5.1

Will be made generic later. See also the related #1620

comment:2 Changed 9 years ago by gracinet

  • Milestone changed from CPS 3.5.1 to CPS 3.5.2

Here's the principle : the administrator can tell the application that a whole subhierarchy is self-contained, meaning that no portlet will display any document from outside of it. This allows CPS to set a correct Last-Modified date and to serve 304 responses. This is enough a seed in most cases so that a reverse proxy can automatically serve without requerying Zope.

Such guaranteed sub hierarchies can be nested. The whole portal is no special case.

This has been in CPSDefault for a while now, and therefore will be in 3.5.1, but there's no proper UI for now. And UI can wait for 3.5.2 or a point release.

Note: See TracTickets for help on using tickets.