Module doesn't properly handle 429 responses from Akamai

Created on 18 October 2022, over 2 years ago
Updated 15 March 2023, about 2 years ago

Problem/Motivation

When Akamai has rate limiting enabled and the limit is met, Akamai returns 429 responses until enough time passes. During that time, any 429 responses are treated by the Akamai module as successful, and nothing more happens. However, the original request failed, and the item was not purged.

Steps to reproduce

On a site using Akamai, make enough requests to pass the rate limit, and see the module receiving 429 responses but not handling them as failures.

Proposed resolution

When receiving a 429 response, re-queue that item so that it can be re-tried. Don't consider it successful and remove it from the queue as long as it's getting a 429 response.

Remaining tasks

Patch needed with suggested implementation.

User interface changes

None.

API changes

None.

Data model changes

None.

✨ Feature request
Status

Fixed

Version

4.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States SamLerner

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024