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.
¿No encuentras una película o serie? Inicia sesión para crearla:
¿Quieres puntuar o añadir este elemento a una lista?
¿No eres miembro?
Contestado por lotrf3
el 8 de febrero de 2015 a las 17:18
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!"Contestado por Travis Bell
el 25 de febrero de 2015 a las 09:56
Hey lotrf3,
Sorry for the late response. Indeed! I'll get this added. Here's the relevant ticket.
Cheers.
Contestado por Travis Bell
el 25 de febrero de 2015 a las 11:10
Fix for this is being pushed live right now. It will be available within a few minutes.
Cheers.
Contestado por lotrf3
el 25 de febrero de 2015 a las 11:29
Thanks!