New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

handle 404 AWS errors due to bucket not found #102

Open

3 tasks

amirbey opened this issue Sep 10, 2021 · 0 comments

Labels

migration squad-pages

Contributor

amirbey commented Sep 10, 2021

User Story

A Pages user requesting a url for a bucket that the proxy cannot find, the user should not receive a 404 error from AWS but from the proxy.

Background (Optional)

Acceptance Criteria

the proxy should provide a custom 404 if the bucket is not found
Change made live via deploy of the proxy

After evaluating, edit this part:

Level of effort - <low/medium/high>

Implementation outline (if higher than "low" effort):

amirbey changed the title ~~handle bucket not found 404 S3 errors~~ handle 404 AWS errors due to bucket not found

amirbey transferred this issue from cloud-gov/pages-builder

apburnes added squad-pages migration labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment