Caching and the gateway feature

Scott Battaglia scott.battaglia at gmail.com
Wed Jun 18 13:54:38 EDT 2008


Gabriel,

The stanard solution is to just rely on the session, though I can see your
point of that mechanism not always being sufficient.

I've created a JIRA issue to track modifying the client such that you can
plug in your own method for determining the Gatewaying:

http://www.ja-sig.org/issues/browse/CASC-58

In the meantime, you could probably modify the client to use a cookie
instead of the session check if you wanted.

-Scott

On Mon, Jun 16, 2008 at 11:49 AM, Gabriel Falkenberg <
gabriel.falkenberg at gmail.com> wrote:

> Hi! I have a question regarding caching in combination with users that
> are not logged in and the gateway feature of CAS.
>
> * I have a site which relies heavily on caching for users that are not
> logged in
> * I don't want to redirect to CAS at every request
> * I don't want to create a session since my environment isn't able to
> cache when a session exists
>
> Is there a standard solution for this?
>
> Best regards
> Gabriel Falkenberg
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080618/c8c2e7d5/attachment.html 


More information about the cas mailing list