fix(images): allow s3.olitt.com host in next/image#12
Merged
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
willymwai
reviewed
Jul 3, 2026
95cac33 to
8ef2987
Compare
willymwai
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hero images render blank on staging/prod shops.
Cause: generated shop media is served from
s3.olitt.com, which is absent fromnext/imageremotePatterns. next/image returns 400 for unlisted hosts (SSRF guard), so the image never loads.Fix: allowlist
s3.olitt.com(/media/**).Evidence: DevTools --
/_next/image?url=https://s3.olitt.com/media/external_images/...→ 400. Worked locally only because media sat on127.0.0.1:9000, which is already listed.