Bug 118615 - Cache in ContentSectionServlet.getItem() ignores languages accepted by client
Summary: Cache in ContentSectionServlet.getItem() ignores languages accepted by client
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: ui
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-18 10:48 UTC by Carsten Clasohm
Modified: 2007-04-18 17:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-07-12 09:09:55 UTC
Embargoed:


Attachments (Terms of Use)

Description Carsten Clasohm 2004-03-18 10:48:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Description of problem:
For mapping URLs to live content items,
ContentSectionServlet.getItem() uses a cache. The key for cache
entries is the URL.

With the multilingual item resolver, one URL can be associated with
different language instances, depending the client's list of accepted
languages.


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


How reproducible:
Always

Steps to Reproduce:
1. In the default content section, create a new Article with French
and English language instances, and publish both.
2. Configure your browser to accept "fr" and "en" in this order.
3. Go to /ccm/content/, click on the Article, and you will get the
French version.
4. Configure your browser to accept only "en".
3. Go to /ccm/content/, click on the Article, reload the page, and you
will still see the French version.


Actual Results:  CMS always displays the language instance which it
displayed for the first client who accessed a URL.

To fix this, the URL and the list of accepted languages should be used
for caching.


Additional info:

Comment 1 Carsten Clasohm 2006-07-12 09:09:55 UTC
Closing old tickets.


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