Shibboleth IdP fails to download metadata then never tries again
Cantor, Scott
cantor.2 at osu.edu
Wed Aug 16 15:11:09 EDT 2017
On 8/16/17, 3:06 PM, "users on behalf of shibboleth655 at lewenberg.com" <users-bounces at shibboleth.net on behalf of shibboleth655 at lewenberg.com> wrote:
> Might that exception be logged in the tomcat log?
Possible but I would doubt it, since it's not a thread Tomcat itself started.
> This is a different issue that I have not been able to resolve. It is
> probably due to my lack of Apache fu, and not anything to do with
> Shibboleth IdP.
I think it's automatic in most cases. Even if ETag isn't there, and I think it is, the Last-Modified header should be, and I think Apache would just automatically handle an If-Modified-Since request. I've had to mess with my server side, but that's because I'm using Jetty and not Apache.
Anyway, it was patched recently to get louder about impending expiration of metadata, so the best workaround for the small chance of a reload thread dying is to use shorter validities and bark if it gets anywhere near expiring, at least going forward. And there should be accessible JSON metrics that can be monitored to detect that also if that's easier.
-- Scott
More information about the users
mailing list