On Tue, Apr 10, 2018 at 2:41 PM, Bryan K. Walton <bwal...@leepfrog.com> wrote:
> What does "Invalid cache cookie length" mean in the cas debug logs?
> For example:
> [Mon Apr 09 16:17:29.340510 2018] [:debug] [pid 7828]
> mod_auth_cas.c(897): [client xxx.xxx.xxx.xxx:64395] Invalid cache cookie
> length for '', (expecting 32, got 0), referer:
> https://<xxx'd out site>/uPortal/f/employee/normal/render.uP
> Is this a problem with the cookie in our CASCookiePath?  Or a problem
> with a cookie in the end user's browser?

It looks like the client sent an empty cookie. In that case I'd expect
a redirect to your CAS server to authenticate again.

It's definitely odd that the cookie is empty. Do you see this often?

- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 

Reply via email to