Hey Angelo,
thanks for the quick reply.
I contacted my server’s tech support – they say don’t perform caching for www-authenticate and tried to re-create the problem – but every time they tried, the feed asked authorization as it should.
They did ask if something in the header of the plugin that would tell the service to re-auth; that would at least explain why some users are able to authorize it and then later become un-authorized.
Is there anything else they can look into? A work-around perhaps? is there any way to diagnose the feed to see why some users can’t access it? Most of them are having problem when trying to access from “PodcastAddict” if that helps.
thank you,
Nitzan
