UC Davis is aware of the issue. A recent change in Chrome code uncovered what looks to be an implementation bug in the ISAPI filter: the HTTP protocol requires an empty line tailing the headers and the filter apparently does not send one. Earlier Chrome code and other browsers seem to be more forgiving of this; the new Chrome code enforces the empty line, otherwise throwing the truncation error.
That sounds to me like the fix is a trivial one character patch. I have a Windows development environment where I'd be willing to patch and rebuild if you can share the source.
M -- 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/cas-user
