A slow Cisco API call finally returns HTTP 403 Forbidden after seve…

Question

A slow Cisco API call finally returns HTTP 403 Forbidden after several seconds. Which consumer action is correct?

Accepted Answer

Read the completed status and take the unrecoverable abort path; do not apply timeout-driven retry just because the call was slow — A late “no” is still a no—not a dropped phone call. When the response finally arrives with 400/403/404, follow the status and stop; do not switch into timeout retry just because the clock ran long.

Answer

Ignore the 403 and retry with exponential backoff as if the client had hit a transport timeout

Answer

Treat elapsed wall-clock time as the only signal and discard the HTTP status entirely

Answer

Upgrade the call to a websocket stream so Forbidden statuses can be delayed indefinitely

A slow Cisco API call finally returns HTTP 403 Forbidden after several seconds. Which consumer action is correct?

Short Explanation

Full Explanation