I am seeing issues within the /3/movie/<id>
endpoint, as well as /3/movie/<id>/release_dates
. Some calls to yield what looks like the first page of search results when called from most clients, always returned as a cloudfront cache hit. curl often works though, with the first attempt giving a cache miss and correct data, subsequent hits cache hit and correct data. But other clients (firefox, nodejs) always get that bad cache data.
There seems to be quite a lot of bad data getting cached into cloudfront, and based on some of the ages I'm seeing, it's still happening.
Example of bad result, from hitting https://api.themoviedb.org/3/movie/10494?api_key=<KEY>
[Perfect Blue (1998)]
Response Headers:
X-Firefox-Http3 h3
age 5517
alt-svc h3=":443"; ma=86400
cache-control public, max-age=19254
content-encoding br
content-type application/json;charset=utf-8
date Fri, 05 Jul 2024 21:27:28 GMT
etag W/"0dab26becaeaf96441045985b7625b3b"
server openresty
vary Accept-Encoding,accept-encoding, Origin
via 1.1 a3b511649bade26170091701ae26b616.cloudfront.net (CloudFront)
x-amz-cf-id s6aZcVNSeuNafeijAtRNxbW7GCIfp6E5L_3EIrxt0OMz3jdVMkoOKA==
x-amz-cf-pop SFO53-C1
x-cache Hit from cloudfront
x-memc HIT
x-memc-age 2549
x-memc-expires 19254
x-memc-key 7006cb590244fb407068b4fb7bbea769
Es fehlt ein Film oder eine Serie? Logge dich ein zum Ergänzen.
Diesen Eintrag bewerten oder zu einer Liste hinzufügen?
Kein Mitglied?
Antwort von tgvarik
am 5. Juli 2024 um 17:45