Question

You are writing a Python script that uses the requests library to push a batch of 200 ACL entries to a controller's REST API. The API uses OAuth2 bearer tokens that expire after 5 minutes, and it enforces a rate limit that returns HTTP 429 with a 'Retry-After' header when exceeded. During long runs some POST calls fail with 401 and others with 429. Which approach correctly handles both failure conditions while completing all 200 pushes?

Accepted Answer

On a 401, request a new bearer token and retry the call; on a 429, sleep for the number of seconds in the 'Retry-After' header before retrying, using a bounded retry loop for each entry.

Answer

Wrap every request in a try/except that catches all exceptions and immediately retries the same call in a tight loop until it returns 200, ignoring status codes and headers.

Answer

Request one token at the start, then send all 200 POSTs concurrently with threads so the batch finishes before the 5-minute token expiry and never triggers rate limiting.

Answer

On any 4xx response, refresh the token and lower the OAuth2 scope, since both 401 and 429 indicate the credential no longer has permission for the ACL resource.