Hello, I am working on a site where a part of the content is protected. We are not using Magnolia authentication for this. We have another SSO application which handles the authentication and authorisation. The way I handle this at present is through a filter which checks the request for a valid cookie failing which the request is redirected to the SSO application. The filter also takes care of updating the cookie expiration etc. This part works well.
I would still like to be able to cache the pages. None of the templates or model classes access the cookie, all the UI personalisation is handled through JavaScript. The ideal scenario would be for our filter to take care of the cookie handling, and Magnolia takes care of caching and rendering the pages while ignoring the cookie header. From what I can see the cache includes the cookie header as well, which wreaks havoc with all the sessions :-). What would be the best way to go about addressing this problem (sub-classing the caching filter, request/response wrappers ...)? Thanks in advance for all help and suggestions. Rakesh -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=1c9860e3-5a24-4b05-a8aa-cb7dac86a6b7 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
