-
Notifications
You must be signed in to change notification settings - Fork 44
Open
Description
Slow down based on 429 Retry-After and Cache-Control max-age.
OK, Retry-After support done directly in the updater; bumping the interval should probably be done as part of a plugin (feels somewhat icky to do it in core); also, the plugin may do other HTTP things, like #246.
Originally posted by @lemon24 in #307
To rethink if this should be a plugin or a core feature:
- ideally, we should store statuses and headers for the last X update attempts (easier to do in core, should happen by default)
- it should be the default and hard to disable by mistake
- for a hosted version of reader, it should not be possible to users to bypass it (so it can't rely on tags)
Related: Cache-Control handling #376
Metadata
Metadata
Assignees
Labels
No labels