I'm trying to do a POST /account/{id}/watchlist
, for which the browser pre-flights a CORS OPTIONS /account/{id}/watchlist
. The OPTIONS request fails with 404. Doing the POST with curl succeeds of course, since they don't pre-flight .
Interestingly enough, OPTIONing and POSTing to /favorite succeeds by routing through IP address 54.243.227.76:443, whereas /watchlist routes through 50.16.214.131:443.
See also this old forum post that addressed this issue.
Un film, une émission télévisée ou un artiste est introuvable ? Connectez-vous afin de créer une nouvelle fiche.
Vous souhaitez évaluer ou ajouter cet élément à une liste ?
Pas encore membre ?
Réponse de lotrf3
le 8 février 2015 à 17h18
Oh, and you might want to take a look at your grammar in your 404 message.
{"status_code":34,"status_message":"The resource you requested could be found."}
...are you sure it could be found? Well, maybe it could actually be found and the server is just being stubborn and refusing to give it to me. "Oh you want this resource? Too bad! 404!"Réponse de Travis Bell
le 25 février 2015 à 09h56
Hey lotrf3,
Sorry for the late response. Indeed! I'll get this added. Here's the relevant ticket.
Cheers.
Réponse de Travis Bell
le 25 février 2015 à 11h10
Fix for this is being pushed live right now. It will be available within a few minutes.
Cheers.
Réponse de lotrf3
le 25 février 2015 à 11h29
Thanks!