This repository was archived by the owner on Jan 28, 2025. It is now read-only.

Description
Describe the bug
So once my app is deployed, if I navigate to example.com/_document AWS returns a "503 request could not be satisfied" error instead of my app. I had expected it to return my 404 page. Not sure if I mis-configured something or if this is happening for other people.
To Reproduce
Steps to reproduce the behavior:
- Go to example.com/_document
- Returns an AWS default 503 message, not my app
Expected behavior
Expected behavior was to return my 404 message. The correct 404 page is returned for /_app and /_error pages.
Additional context
Going to any sub-directory of /_document returns the correct behavior (e.g. /_document/blah)