For those interested in the 'correct' way to use ETags in portlets (correct here meaning an HTTP 304 is returned when it should be and no error messages are thrown in uPortal), I added information and code examples from way too much investigation in https://wiki.jasig.org/display/UPM41/Portlet+Caching.

This should fix the Calendar Portlet's ETag caching and be a model we could use for more cache validation of JSON Resource requests in portlets.

--
James Wennmacher - Unicon
480.558.2420


--
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to