2017-06-14 15:45:14 UTC
my nix-index (https://github.com/bennofs/nix-index) project has the problem
that it seems to almost reliable trigger a 500 internal server error on `
Here is the curl log from when that happens:
Note how the error goes away right as (what I assume is) the cloudfront
cache TTL for the 500 error page expires (5 minutes, note the Age header. I
ran curl every 20 seconds and the `Age` header went up continously starting
from ~`0`, the gist only shows the last 3 runs).
I believe that the bug affects both nar's and narinfos.
At https://forums.aws.amazon.com/message.jspa?messageID=689787, it is said
"It looks like there was an error getting the Metabucket partition, and as
a result the request failed. This is a defined behavior and happens from
time to time.
During normal operations it is not unusual to encounter an occasional error
from S3. When using CloudFront with S3, when a user requests an object,
CloudFront requests the same object from S3 and caches it for future users.
Should S3 encounter an error and is unable to provide the object to
CloudFront at that time it sends the error to CloudFront, which then sends
the error to the end user."
Is the cache perhaps misconfigured, in that it caches 500's as well, making
Thanks in advance,