Closed atesgoral closed 7 years ago
@titaniumbones The feature is already in this PR. I broke my own principle of keeping PRs topical and did the new feature + refactoring in one shot.
@atesgoral did you see @mhucka 's notes about the 503? Does it give you any concerns? I guess now that you're not getting the 503's it's hard to check the Retry-After header.
Yeah, it's too late now to check if there was a Retry-After header.
Wishfully thinking that it was just a fluke :)
It would be interesting to hear from the IA folks what they think about the 503 responses.
I'm looking around for a cloud-based API caching gateway. Amazon's API Gateway can be configured to cache API responses from an endpoint for a certain amount of time, but it's not available on the free tier. Also, it's optimistic to think that there will be a lot of cache hits to be able to take advance of an API response cache.
Realized I forgot to check the URL when the popup initially loads :) Adding that now.
Just a quick note to say I haven't heard anything back yet. Will keep you posted. I'm sure the IA people are beyond busy these days ...
@mhucka, @titaniumbones It could be best if I just leave the feature code in, but just disable the CDX lookup so that we can at least merge this PR with all the refactoring that was done. Then it would be just flipping a switch to re-enable the lookup.
@atesgoral Sounds like a most excellent plan!
URL checking disabled.
Excellent, merging. @mhucka, if somehow you hear back form Jefferson that the problem is unrelated to server load, we can revert 18e69ee and take this live at any point.
Should i delete the branch or keep it open?
Safe to delete! Deleted.