Hi,
I was just wondering what the recommended way of caching is. Is there only ETag? Should one use ETag for caching?
As far as I can tell If-Modified-Since is not supported. Is there any plans of making the HTTP response include the last-change date so I can send requests with If-Modified-Since header?
Cheers, Reinhard
¿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 rednoah
el 19 de noviembre de 2013 a las 02:11
Actually ETag doesn't seem to work.
Request is setting If-None-Match correctly but server is responding with 200 OK + data instead of just rending back a 304 Not Modified: http://snag.gy/mIkt9.jpg
Contestado por Travis Bell
el 19 de noviembre de 2013 a las 10:12
Have you taken a look at this thread: https://www.themoviedb.org/talk/5162e6e8760ee374b610b24e
Contestado por rednoah
el 19 de noviembre de 2013 a las 20:21
(my bad, had If-Modified-Since set which apparently cancels out If-None-Match)
Contestado por rednoah
el 19 de noviembre de 2013 a las 21:16
Got it working now. Just need to make sure If-Modified-Since is not set if If-None-Match is set. Though why the above curl call didn't work is beyond me...
Contestado por rednoah
el 19 de noviembre de 2013 a las 21:22
If I get back "304 Not Modified" does the request count towards the rate limit?
Contestado por Travis Bell
el 21 de noviembre de 2013 a las 22:42
Hi rednoah,
It will count towards the rate limit. The benefit is the saved transfer on both our end and your client(s). This results in less resources being used all round and just being a better API consumer.
Contestado por caprica6
el 21 de enero de 2014 a las 09:50
I am trying to use etags but it does not seem to work for me.
Can anyone see what I am doing wrong?
So here we can see the etag is:
Now I pass that same etag in the If-None-Match header...
I still get a 200 response and the entity.
What have I missed?
Contestado por Travis Bell
el 21 de enero de 2014 a las 19:09
I can replicate this, I suspect the change was caused when we removed Varnish from our stack. I'll have to spend some time digging into this and seeing if we can take care of this properly at the app level.
Here's the relevant ticket.
Cheers.
Contestado por rofrantz
el 27 de marzo de 2014 a las 11:15
Is this problem solved because I that same issue too.. Even if I send the If-None-Match I still get 200
Contestado por Travis Bell
el 27 de marzo de 2014 a las 11:33
No, the problem is not fixed yet. The ticket is still open.
Contestado por mchiasson
el 20 de noviembre de 2017 a las 12:17
3.5 years later, still looks like etag isn't working:
curl -i -H Accept:application/json -H If-None-Match:df2617d2ab5d0c85ceff5098b8ab70c4 -X GET 'https://api.themoviedb.org/3/genre/movie/list?language=en-US&api_key=API_KEY'
I still get 200
Contestado por Travis Bell
el 20 de noviembre de 2017 a las 14:43
That is correct, it hasn't been fixed yet. I do not have an ETA for this issue at this time.
Contestado por rlaphoenix
el 21 de febrero de 2018 a las 23:33
Still not fixed? :/ I really need this.
Contestado por Travis Bell
el 25 de febrero de 2018 a las 12:07
By the way,
If-None-Match
works on most API calls now (the ones that return anETag
). I'll try to find some time to get the remaining methods that aren't returning anETag
completed soon.Responds with a regular
200
response, and if we make a call withIf-None-Match
...We're properly returning a
304
.Cheers.