What you're doing is saying "any _new_ results returned from this view are
uncacheable", but that doesn't impact the results that are in the cache
already.
Read up on this section to see how to "invalidate" the existing cache:
https://docs.djangoproject.com/en/1.4/topics/cache/#cache-versioning
Thanks Chris,
That's exactly what I thought I was doing. Can you please tell me what
missed? How, exactly do unclear the cache; if that's not what I'm currently
doing?
On Monday, December 17, 2012, Chris Cogdon wrote:
> You'll need to clear the cache. Remember, once the view is cached, django
>
You'll need to clear the cache. Remember, once the view is cached, django
wont go down to the view until the cache thinks the content has expired.
On Monday, December 17, 2012 5:14:56 PM UTC-8, Dwayne Ghant wrote:
>
> Hello All:
>
> I have a python view that I'm building but the for some strang
Hello All:
I have a python view that I'm building but the for some strange reason the
view keeps caching. Just to give an example:
@api_view(['POST'])
@parser_classes((XMLParser,))
@cache_page(0)
@cache_control(private=True)
def test_view(request, format=None):
return Response({'received
4 matches
Mail list logo