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

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.

-----BEGIN PGP SIGNATURE-----

Version: GnuPG v2.0.22 (GNU/Linux)

Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJS0ArzAAoJECKM1e+fkPrXfuAH/1LWCfDteoZw6lVEIi2MvtOm

EuiGfqA1yPN1DnHT7uKs1tR/dwY/plgDSTHt0HkdA6Y6UOvLXeeLA/1tlv9NTSRN

AvM152t1WsoMK7XL7Sn2bEQBgDst7yStk7fwdKdf80vyGkNduTHtcYYSL2rKHsLk

zgAmoT0Ib8JBWZI3+yz86e8kN4B56hAf9OLxnVP+HIY5aPVfIjf88ukRpo8Txv2h

py+kz9fl5lTHPnxa3UYiI3iOxcXA5JZno0qmq3q/YLdsMFiBY/cZSE8O3bl1/gqq

zs4tNrLCsFyD4psCrHtsPUHdhbWKHSGWHYmg9LYnj58NTBilDzgD5MZx85Vy8vQ=

=Lium

-----END PGP SIGNATURE-----

_______________________________________________

gatein-dev mailing list