Encoding Error for Web folder

What to do

• Check whether you use imgix in us. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2024-02-26 17:41 UTC and 2024-01-22 21:00 UTC may need a replay.

• Subscribe to imgix's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=imgix works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from imgix 2

1. resolvedJan 22, 2024, 9:00 PM UTC

   We have identified the issue and are currently applying a fix. The rendering service is not affected.

   provider

2. postmortemFeb 26, 2024, 5:42 PM UTC

   Postmortem What happened? On January 22, 2024, 07:38 UTC, some Web Folder requests to the imgix service began to return a 403 response. By 11:56 UTC, the issue had been completely resolved. How were customers impacted? Between 07:38 UTC and 11:36 UTC, several requests to web folder sources began to return a 403 error. This affected a small amount of assets \(<0.1%\). What went wrong during the incident? A service update caused an issue with web folders with directories using double slashes at the Origin URL \(//\). This update caused an encoding error, leading to 403 responses for Origins matching the double slash pattern. A fix was pushed to resolve this URL pattern, allowing us to fetch images from affected Origins. What will imgix do to prevent this in the future? We will update our tests to catch encoding issues in the future.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.