You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The central config spec has recently been updated to say that regardless of what the Cache-Control headers are, agents should only retry at a maximum every 5 seconds to fetch the central configuration. I.e. if the Cache-Control headers specify a value less than 5, the default retry interval should be used.
A question that came up while implementing this. The spec says
If the Cache-Control header is zero (or less than zero)
However, the relevant RFC says that max-age is of type delta-seconds:
The delta-seconds rule specifies a non-negative integer, representing time in seconds.
So, negative values aren't allowed. Is the intention of the spec to behave reasonably in the face of misbehaving servers/proxies, or could we simplify this a bit?
FWIW, the Python agent behaves as spec'd by accident, as the regex fails to parse negative values and falls back to the default interval of 300s.
Description
The central config spec has recently been updated to say that regardless of what the Cache-Control headers are, agents should only retry at a maximum every 5 seconds to fetch the central configuration. I.e. if the Cache-Control headers specify a value less than 5, the default retry interval should be used.
Agent Issues
The text was updated successfully, but these errors were encountered: