[PLIP-Advisories] Re: [Plone] #9236: Include CachableRedirects or equivalent functionality so that 301 redirects don't pound Zope

2009-07-02 Thread plip-advisories 
#9236: Include CachableRedirects or equivalent functionality so that 301
redirects don't pound Zope
+---
 Reporter:  jonstahl|Owner: 
 Type:  PLIP|   Status:  closed 
 Priority:  minor   |Milestone:  4.0
Component:  Infrastructure  |   Resolution:  wontfix
 Keywords:  |  
+---
Changes (by esteele):

  * status:  reopened = closed
  * resolution:  = wontfix


Comment:

 Rejected for Plone 4.0 by FWT vote.

-- 
Ticket URL: https://dev.plone.org/plone/ticket/9236#comment:17
Plone http://plone.org
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

[PLIP-Advisories] Re: [Plone] #9236: Include CachableRedirects or equivalent functionality so that 301 redirects don't pound Zope

2009-06-30 Thread plip-advisories 
#9236: Include CachableRedirects or equivalent functionality so that 301
redirects don't pound Zope
+---
 Reporter:  jonstahl|Owner:  
 Type:  PLIP|   Status:  reopened
 Priority:  minor   |Milestone:  4.0 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by erikrose):

 FWT Vote: +1 as long as purging is implemented. In response to rossp,
 IIRC, this can't be done straightforwardly in CacheSetup due to the really
 wacky way into which Plone fires off redirects. It all funnels through the
 error reporting template, which then checks to see if the error is 404.
 I would like to hook the config into CacheSetup, perhaps via alecm's
 suggestion of an empty skin template.

-- 
Ticket URL: https://dev.plone.org/plone/ticket/9236#comment:16
Plone http://plone.org
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories