[WARN] HttpClient - Error Sending message to url endpoint
[https://.../login/index.php]. Error is [Server redirected too many times
(20)]
...
Now, our test Moodle server is just using a self-signed certificate.
We were thinking that perhaps this is a factor in the redirect loop --
on the logout, CAS tries to communicate with Moodle, but can't,
because it doesn't trust the certificate, so the result is a redirect
loop.
Is that possible?
Doubtful. If there is a certificate trust problem, the connection would
be closed long before the HTTP request could be sent, which would
preclude getting a 302 response to begin a redirect loop.
Or is there something else going on here?
I'm wondering whether index.php is sending a 302 redirect to another URI
that's expecting a session cookie, for example, and since the HttpClient
component knows nothing about keeping state, it's bounced back to
index.php and the loop begins. The proper behavior is for your
index.php to treat POST different from GET, which would allow the logout
POST to end, simply, in a 200. Hopefully you can translate that advice
into Moodle configuration.
For what it's worth, we see this behavior a lot around here and I've
attributed it to the behavior above. It's fairly innocuous other than
needlessly tying up server resources, though it suggests the client
isn't participating in single sign-out. If you care about single sign
out, then it's of greater concern.
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
