Kombinierte Ansicht Flache Ansicht Baumansicht
Threads [ Zurück | Nächste ]
toggle
Joe Kosik
Liferay 6.x Portlet /Disabling web browser cache:SOLUTION
21. September 2012 18:20
Antwort

Joe Kosik

Rang: New Member

Nachrichten: 1

Eintrittsdatum: 21. September 2012

Neue Beiträge


(note: I am sure the Liferay admins would find this one as no surprise)

For those JSF / Primefaces portlet developers (fellow J2EE programmers) out there...

Liferay 6.x Portlet Development / Disabling web browser cache: SOLUTION / WORKAROUND

To disable the web browser caching of your primefaces / JSF portlets in Liferay...
... the answers turns out to be one of configuration. However, this turns-off web browser caching for ALL portlets in a given Liferay 6.X portal.

1. Open up a file editor
2. Paste in the following content:
__________________________________________________________________________________
 1
 2##
 3## Browser Cache
 4##
 5
 6    #
 7    # Set this to true if you want the portal to force the browser cache to be
 8    # disabled. It will only disable the cache for the rendered HTML response
 9    # It will not have an impact on static content or other resources.
10    #
11    browser.cache.disabled=true
12
13    #
14    # Set this true if you want to disable the cache for authenticated users.
15    # This property is not read when the property
16    # "browser.cache.signed.in.disabled" is true. This is useful to ensure that
17    # authenticated users cannot go to the sign in page by clicking on the back
18    # button in their browsers.
19    #
20    browser.cache.signed.in.disabled=true

__________________________________________________________________________________
3. Save as: [portal-ext.properties]
4. With your Liferay 6.X Portal shutdown, copy the file:[portal-ext.properties] into the directory:[/alpha/beta/gamma/.../omega/liferay-portal-6.1.1-ce-ga2/tomcat-7.0.27/webapps/ROOT/WEB-INF/classes]
5. Restart Liferay Server paying attention to the logs for any startup / configuration errors

6. To test / confirm, using Firefox with Firebug plugin, access any portlet page, and check your Firebug plugin:
6.1 tab: / sub-tab:
6.2 expand out the GET URL
6.3 click on sub-sub-tab:
6.4 subsection:[Response Headers] should look something like this:
-------------------------------------------------------------------
 1
 2    Server    Apache-Coyote/1.1
 3    Set-Cookie    JSESSIONID=5DA1E6DCAB27D2BF4206D65FEC45CEC6; Path=/; HttpOnly GUEST_LANGUAGE_ID=en_US; Expires=Sun, 22-Sep-2013 00:50:10 GMT; Path=/
 4    Content-Encoding    gzip
 5    Expires    Thu, 01 Jan 1970 00:00:00 GMT
 6    Cache-Control    private, no-cache, no-store, must-revalidate
 7    Pragma    no-cache
 8    Liferay-Portal    Liferay Portal Community Edition 6.1.1 CE GA2 (Paton / Build 6101 / July 31, 2012)
 9    Content-Type    text/html;charset=UTF-8
10    Transfer-Encoding    chunked
11    Date    Sat, 22 Sep 2012 00:50:10 GMT

-------------------------------------------------------------------
6.5 pay attention to "Expires", "Cache-Control", and "Pragma"

-------------------------------------------------------------------------------------------------------
Primefaces (v3.3.1), Mojarra JSF API Implementation 2.1.3 (b02-FCS), Liferay 6.1 CE (Tomcat 7.0.27), Linux operation system

Mazhar Alam
RE: Liferay 6.x Portlet /Disabling web browser cache:SOLUTION
21. September 2012 20:40
Antwort

Mazhar Alam

Rang: Regular Member

Nachrichten: 201

Eintrittsdatum: 25. November 2011

Neue Beiträge

It seems helpful...
Neil Griffin
RE: Liferay 6.x Portlet /Disabling web browser cache:SOLUTION
27. September 2012 13:33
Antwort

Neil Griffin

LIFERAY STAFF

Rang: Liferay Legend

Nachrichten: 2363

Eintrittsdatum: 26. Juli 2005

Neue Beiträge

Hi Joe,

Thanks for the post. emoticon When you get a chance, could you comment here with a typical use-case that developer will run into with PrimeFaces portlets in which they would want to disable caching?

Neil
Michele Giacobazzi
RE: Liferay 6.x Portlet /Disabling web browser cache:SOLUTION
23. Januar 2013 05:34
Antwort

Michele Giacobazzi

Rang: Junior Member

Nachrichten: 40

Eintrittsdatum: 9. September 2011

Neue Beiträge

I have the "inverse" problem. All request receive a "no-cache" response, but I'd like to cache static files.

How could I activate browser cache?

I'm running liferay 6.1.1 bundled with tomcat
Manuel Hoyos
RE: Liferay 6.x Portlet /Disabling web browser cache:SOLUTION
30. Januar 2013 23:35
Antwort

Manuel Hoyos

Rang: Junior Member

Nachrichten: 58

Eintrittsdatum: 10. Juni 2012

Neue Beiträge

Michele Giacobazzi:
I have the "inverse" problem. All request receive a "no-cache" response, but I'd like to cache static files.

How could I activate browser cache?

I'm running liferay 6.1.1 bundled with tomcat



I have a same problem. In the documents portlet not download with internet explorer

What's the problem?

Thanks
Juan Gonzalez
RE: Liferay 6.x Portlet /Disabling web browser cache:SOLUTION
31. Januar 2013 01:24
Antwort

Juan Gonzalez

LIFERAY STAFF

Rang: Liferay Legend

Nachrichten: 2892

Eintrittsdatum: 28. Oktober 2008

Neue Beiträge

If you're using 6.1.1, probably your hitting this issue:

http://issues.liferay.com/browse/LPS-29645

You can download patched version here:

https://www.lcepatchers.org/downloads
Jan Tošovský
RE: Liferay 6.x Portlet /Disabling web browser cache:SOLUTION
7. Februar 2013 09:19
Antwort

Jan Tošovský

Rang: Expert

Nachrichten: 424

Eintrittsdatum: 22. Juli 2010

Neue Beiträge

I need it for session scoped beans - when global settings change between two views and you return to the original page, it is still displaying cached/outdated values.
Imagine a composed page. There are common options (e.g. time range) on the right and body area in the midddle (e.g. montly report). When you click on the link in that report to get detailed version, you can change that time range there as well. If you do it, the detailed report is updated.
But when you click the back browser button, the montly report data isn't updated to the updated time range. Everything is fine when you refresh the page (F5).

Thanks for the proposed solution, but clearing the cache globally is not acceptable for me...

Jan