Opened 2 years ago
Last modified 2 years ago
#34048 closed Cleanup/optimization
Do not add cache control header if is set to false or a falsy value — at Initial Version
| Reported by: | Wiktor | Owned by: | nobody |
|---|---|---|---|
| Component: | Utilities | Version: | dev |
| Severity: | Normal | Keywords: | cache control |
| Cc: | Wiktor, Jan Urban, Flavio Curella | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Currently when one sets no_cache to a falsy value, e.g.:
@cache_control(no_cache=False)
def some_view()
pass
Cache-Control header will be set to no_cache=False.
This might be confusing and might lead to a security issue.
Note:
See TracTickets
for help on using tickets.