404 page doesn't actually 404

[pettazz]

On a url that doesn't exist, we redirect to the 404 page /404/index.html that displays a visible "not found message" but the responses are never actually 404, but instead a series of redirects and eventually a 200:

$ wget https://warrantynowvoid.com/peepee-poopoo
--2019-06-08 12:45:38--  https://warrantynowvoid.com/peepee-poopoo
Resolving warrantynowvoid.com... 52.85.139.144, 52.85.139.243, 52.85.139.127, ...
Connecting to warrantynowvoid.com|52.85.139.144|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: /peepee-poopoo/ [following]
--2019-06-08 12:45:38--  https://warrantynowvoid.com/peepee-poopoo/
Reusing existing connection to warrantynowvoid.com:443.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: /404.html [following]
--2019-06-08 12:45:38--  https://warrantynowvoid.com/404.html
Reusing existing connection to warrantynowvoid.com:443.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: /404/ [following]
--2019-06-08 12:45:38--  https://warrantynowvoid.com/404/
Reusing existing connection to warrantynowvoid.com:443.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'peepee-poopoo'

peepee-poopoo                           [ <=>                                                             ]   2.10K  --.-KB/s    in 0s

2019-06-08 12:45:39 (24.1 MB/s) - 'peepee-poopoo' saved [5775]

[pettazz]

Looks like this may be a limitation of Amplify as a platform? https://forums.aws.amazon.com/message.jspa?messageID=905089