--
DAVID A. CURRY, CISSP
DIRECTOR OF INFORMATION SECURITY
INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300 x4728 • david...@newschool.edu
--
- 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+unsubscribe@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/367058ff-b38a-43ac-af96-d712c91b1e99%40apereo.org.
Thank you for that explanation. Our original CAS4 setting was maxHttpHeaderSize="16384", but after the CAS5 upgrade that failed right away as it was too small.
Then we did go to the CAS5 documentation setting that I reference below, and recently we were questioning the value of the setting. We have not tried to shrink for alternate smaller values.
We are actually running CAS 5.0.5 at the moment, if you see my other posts then you will see why.
BTW – you have a great CAS5 deployment site: https://dacurry-tns.github.io/deploying-apereo-cas/introduction_overview.html
If people have not seen this, then they should definitely check it out!!!
Duane Booher
Northern Arizona University
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.