-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 All, We've seen a request to add the possibility for administrators to set the cache-control to something else than "no-cache". I've drafted a commit that would allow it to be a portal configuration, and submitted the PR https://github.com/gatein/gatein-portal/pull/759/files . I was wondering if anyone knows if there's any reason why this entry was set to "no-cache" explicitly, and what could be the side effects of such change. I've debugged it a bit, and it seems that non-asset requests reaches this code (as in, code that returns an HTML, not images/css/javascript), so, I don't think this is related to the assets. As a side-question, this configuration option named "Cache Control" might seem a bit cryptic to anyone looking at it without the context, but I haven't figured out a good way to provide a help tip about it. Is there a facility that I could use, to explain what this option does, possibly linking to the RFC that lists all the options? Thanks! Juca. _______________________________________________ gatein-dev mailing list gatein-dev(a)lists.jboss.org (mailto:gatein-dev@lists.jboss.org) https://lists.jboss.org/mailman/listinfo/gatein-dev

[...] the same URL yields different results [...]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 01/20/2014 10:39 AM, Julien Viet wrote: > by default portal pages are not cached because they can be > personalised for the current user, i.e two distinct user may not > see the same markup. Cache servers sitting between the user and the server might cache GET requests based on this header. So, if the same URL yields different results depending on the user, then it might be a problem. Is this the case? Should we then block this feature, or should we just put a big fat warning when an admin touches this property? Juca. _______________________________________________ gatein-dev mailing list gatein-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/gatein-dev

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 01/20/2014 11:50 AM, Peter Palaga wrote: > Hi Juca, > > > [...] the same URL yields different results [...] > > One URL can also return distinct language versions of the page > depending on the visitor's preferences (not sure if these are > stored in a cookie or JCR). -- PP > Ok, so, another situation might be that one user gets a page in EN, with the cache headers, and gets the cached version once he changes to, say, ES. Not good, but not the end of the world as well, I guess. The other scenario seems more critical to me, as a cached page might leak some information from one user to another user. But just a reminder: the default setting is still "no-cache", so, an administrator would have to explicitly and actively set the value to a caching value. Arguably, the administrator would be aware of such cases (ie: web accelerator/cache between the server and the user, pages in multiple languages, ...). I guess the question than changes to: is it worth having this feature? Or is the risk just too high for the benefit? Juca. _______________________________________________ gatein-dev mailing list gatein-dev(a)lists.jboss.org (mailto:gatein-dev@lists.jboss.org) https://lists.jboss.org/mailman/listinfo/gatein-dev