On 01/06/2017 11:26 PM, Jeff Willette wrote: > Wy would this not help the efficiency of the downstream caches? Is it > because the request has already passed through them with the cookies > intact? and when it comes back through the response they have no way to > know they have been stripped?
That's correct. Stripping cookies from the request in Django is far too late to have any effect on an external cache. If the request has reached Django, then it's already passed through any external caching proxies, with all cookies, and the cache has already decided not to serve a cached response. (And if the cache holds on to the response, it'll associate with the the request it saw, which still had all its cookies). Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d1383be4-749e-3183-4354-ac0047bd0517%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
