2013-04-09, 20:37
The caching that's affecting you is happening at the AniDB end of things.
This is the URL the scraper uses:
http://api.anidb.net:9001/httpapi?reques...1&aid=9418
...No episodes are currently listed in the XML despite clearly being on the website.
Nothing the scraper can do to fix that.
I don't know of anyway to invalidate the cache at their end (and I doubt they'd be very happy if I did and implemented it).
This is the URL the scraper uses:
http://api.anidb.net:9001/httpapi?reques...1&aid=9418
...No episodes are currently listed in the XML despite clearly being on the website.
Nothing the scraper can do to fix that.
I don't know of anyway to invalidate the cache at their end (and I doubt they'd be very happy if I did and implemented it).
