René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Potential request spamming after initial cooldown surpassed","articleBody":"Hey Folks.\n\nWe recently had a situation in one of our environments, where usage of the `refresh`-api somehow overwhelmed our `azconfig` instances, which then gave HTTP `429 Too-many-requests`, occasionally - especially during peak-load times of our app.\n\nWe used [1.0.0-preview4](https://github.com/Azure/AppConfiguration-JavaScriptProvider/releases/tag/1.0.0-preview.4) at this time and thx to @lorenzadomat found out, that the refresh-interval might be ignored, somehow.\n\nI then took the opportunity to narrow this even further down. Seems like starting with [1.1.0](https://github.com/Azure/AppConfiguration-JavaScriptProvider/releases/tag/1.1.0) / [b1cf8099fbf8737de3d38299be2871d4547c7cac ](https://github.com/Azure/AppConfiguration-JavaScriptProvider/pull/65/commits/b1cf8099fbf8737de3d38299be2871d4547c7cac), this behavior dissappeared.\n\nLooks like prior 1.1.0, sentinel keys got queried every time, after the initial `refreshIntervalInMs` has been surpassed - before this has happened, everything works as expected - that's why this was not that easy to reproduce ;)\n\nJust wanted to let you know about this, especially as this might have been fixed \"by accident\" and not on purpose.\n\nI have a simple repro over at my [repro-repo](https://github.com/earloc/repros/tree/main/src/azure/AppConfiguration-JavaScriptProvider#httpsgithubcomazureappconfiguration-javascriptproviderissues137), which hopefully showcases the problem clear enough.\n\nLet me know if this somehow might help in preventing some future regressions. We will probably notice, at least.\n","author":{"url":"https://github.com/earloc","@type":"Person","name":"earloc"},"datePublished":"2024-11-30T19:00:44.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/137/AppConfiguration-JavaScriptProvider/issues/137"}