# Django caching useless with CSRF protection?

**URL:** <https://forum.djangoproject.com/t/django-caching-useless-with-csrf-protection/26172>\
**Category:** Deployment\
**Created:** [December 14, 2023, 7:09pm UTC](https://forum.djangoproject.com/t/django-caching-useless-with-csrf-protection/26172 "2023-12-14T19:09:46Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [December 15, 2023, 8:10pm UTC](https://forum.djangoproject.com/t/django-caching-useless-with-csrf-protection/26172/4 "2023-12-15T20:10:37Z")

</div>

A search would be “safe” in this context if there is no data being written. (No objects being created or updated, and no “user status” change such as a login/logout.)

I would have the opinion that this view would be considered safe.

---

_[View the full topic](https://forum.djangoproject.com/t/django-caching-useless-with-csrf-protection/26172)._
