Herman Reintke wrote: > LS, > > I indeed used the apache http server (mod_header) to include the > cache-control directive. > Disadvantage however is that I needed to set cache-control no-cache for > all responses as apache has no knowledge on what is being responded. And > a lot of the responses can be cached without any problem. >
Well, since you only mentioned cache control for all jetspeed pages, I thought mod_header was the most appropriate :) (using a <location> block, you can make your cache statements apply only to *.psml URI and thus still cache your images, css etc...). It's seems like you'd like some more fine grain control on page caching from jetspeed. Can you elaborate a bit on how you would like to manipulate the cache settings ? per PSML page, per portlet, per portlet instance, per authenticated user ? It could be an interesting feature to add. > Randy : without the proxyserver it indeed looks OK as distributed, > although I did not check all. > > Kind regards, > > Herman Reintke > > >> >> Le 17 déc. 05 à 16:31, Randy Watler a écrit : >> >>> On Sat, 2005-12-17 at 11:23 +0100, Herman Reintke wrote: >>> >>>> LS, >>>> >>>> I am using the binary J2 installation with the Derbydatabase. On >>>> top of that an Apache webserver is installed to be able to access >>>> the J2 Portal, together with my other installs/pages using port 80. >>>> >>>> 2/ Caching >>>> Sometimes I only have access to my J2 environment from behind a >>>> proxyserver. With the standard install I noticed several occasions >>>> when I got "old pages" which were only refreshed to the correct >>>> onces after a "forced" get by the browser. I only checked a few >>>> pages pages but the most obvious were : >>>> - main page, I regulary got the "admin logged in page" instead of >>>> the anonymous page where youneed to login. >>>> - Portal site manager >>>> When working with the PSM The portal site browser and portal site >>>> detail are not updated when selecting. >>>> I've come around this behaviour nor to forcing all responses to >>>> have the directive "cache-control no-cache'. >>>> Checking the apache access log I see for example the portal site >>>> detail alway being requested as : GET /jetspeed/portal/ >>>> _ns:YXBkYi0xfGMwfGQwfGY_/Administrative/site.psml, which indeed >>>> would allow a proxyserver to serve cached content. >>>> Question : >>>> - Are there any specific cache-control options to be set in J2 ? >>> >>> >>> I am not aware of any global configurations that can be set to add >>> headers to all outgoing responses. Have you been able to verify that >>> all >>> is well without the proxyserver in place? >>> >> >> The easiest way to manage cache control issues is to implement the >> caching policy >> through the Apache HTTP server using mod_expires and possible >> mod_header. >> >> Check the HTTPD documentation for usage of these 2 modules. >> -- Raphaël Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
