Re: [gatein-dev] Cache-Control - change it to be a per-portal configuration

-----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