Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 107721 - Item preview pages should not be cached
Item preview pages should not be cached
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Archit Shah
Jon Orris
Depends On:
Blocks: 100952 106597
  Show dependency treegraph
Reported: 2003-10-22 09:36 EDT by Daniel Berrange
Modified: 2007-04-18 12:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-07 18:14:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Berrange 2003-10-22 09:36:32 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314

Description of problem:
The old ItemDispatcher used to disable caching when previewing draft content
items. The new ContentSectionServlet lost this behaviour and now  allows both
published & draft preview pages to be cached. THis is wrong because it means
authors don't see their changes unless they force the browser to reload the page
& discard the cached copy.

This must be applied to 6.0 & rickshaw

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create an item
2. Preview the item
3. Make a change to the item
4. Preview the item again

Actual Results:  The change from step 3 doesn't appear

Expected Results:  The change from step 3 does appear

Additional info:

Example *incorrect* cache headers on preview:

dan@camden$ wget -S http://dev:9068/ccm/content/preview/foo.en
--14:34:51--  http://dev:9068/ccm/content/preview/foo.en
           => `foo.en.1'
Resolving dev... done.
Connecting to dev[]:9068... connected.
HTTP request sent, awaiting response... 
 1 HTTP/1.0 200 OK
 2 Server: Resin/2.1.10
 3 Cache-Control: public, max-age=1123200
 4 Expires: Tue, 04 Nov 2003 13:34:52 GMT
 5 Last-Modified: Wed, 22 Oct 2003 13:34:52 GMT
 6 Set-Cookie: JSESSIONID=aSOBZhl2LsKc; path=/
 7 Content-Type: text/html; charset=UTF-8
 8 Date: Wed, 22 Oct 2003 13:34:53 GMT

    [ <=>                                                                      
                                           ] 4,622          4.41M/s             

14:34:53 (4.41 MB/s) - `foo.en.1' saved [4622]


Headers 3,4,5 should in fact be:

 3 Pragma: no-cache
 4 Cache-Control: must-revalidate, no-cache
 5 Expires: Thu, 01 Jan 1970 00:00:00 GMT
Comment 1 Archit Shah 2003-11-05 13:36:55 EST
fixed at 37713 for dev and 37715 for 6.0.x

Note You need to log in before you can comment on or make changes to this bug.