GET requests to externals.io result in 404 responses

[ramsey]

To reproduce:

curl -I https://externals.io

This will result in something like:

HTTP/2 404
date: Mon, 24 Feb 2020 16:32:20 GMT
content-type: text/html; charset=utf-8
set-cookie: __cfduid=d5de99337fcf1c2db5b10cc2640291cbe1582561940; expires=Wed, 25-Mar-20 16:32:20 GMT; path=/; domain=.externals.io; HttpOnly; SameSite=Lax; Secure
x-amzn-requestid: 85376a81-6b7b-485a-be3a-65858a3188e5
x-amz-apigw-id: IaQXOF6pjoEFqhg=
x-powered-by: PHP/7.3.2
x-amzn-trace-id: Root=1-5e53fa94-aad7a018d5d34e34e9a88e2a;Sampled=0
via: 1.1 7c79be60fcabd36655f1da4928e2adea.cloudfront.net (CloudFront), 1.1 e9485f60105658dfd8d6d4dbc070260a.cloudfront.net (CloudFront)
x-amz-cf-pop: ORD52-C1
x-cache: Error from cloudfront
x-amz-cf-pop: ORD51-C1
x-amz-cf-id: G3FYMUjEHCUHns-uFW76u4r9KO4CLSPleBAYKIujiZLpTpWkSVKPiA==
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 56a2d5befc3654f6-ORD

I expect it to return a success status (such at 200 OK).

[ramsey]

Just to be clear, the page loads just fine, but the client is receiving a 404.

[mnapoli]

Ohh that's weird!

What's even weirded is that in the browser we get a 200 🤔

I have CloudFlare setup to point to CloudFront, which isn't necessarily necessary. But I don't understand what would cause the problem.

[ramsey]

I only noticed this because I have a Wayback Machine extension installed in my browser, and it "randomly" pops up while I'm browsing externals.io.

When it popped up this time, it's because the following asset resulted in a 404: https://cdn.jsdelivr.net/dist/instantsearch.min.js.map

However, when I make HEAD requests to externals.io using curl, I consistently get a 404.