SP downloading and xmldsig-validating remote XML metadata on every start

[Cantor, Scott]

I tested and verified it's still doing good things. My guess is that you (or whomever) don't have Etag support configured on the server and it's not able to detect that the resource hasn't changed,

The logic works by issuing a conditional GET based on the Etag stored on disk (the cached file with a .tag extension) and if that comes back clean, it doesn't download the new one, uses the backup and then you get the benefit.

No Etag or at least no tag file, and you get a new download, so it doesn't use the backup unless the main fetch fails.

-- Scott