Django sitewide cache and axes middleware ordering problem

[sertac]

hi,

according to Django docs
https://docs.djangoproject.com/en/4.1/topics/cache/#the-per-site-cache
No, that’s not a typo: the “update” middleware must be first in the list, and the “fetch” middleware must be last. The details are a bit obscure, but see Order of MIDDLEWARE below if you’d like the full story.

according to axes docs
# AxesMiddleware should be the last middleware in the MIDDLEWARE list.
# It only formats user lockout messages and renders Axes lockout responses
# on failed user authentication attempts from login views.
# If you do not want Axes to override the authentication response
# you can skip installing the middleware and use your own views.
'axes.middleware.AxesMiddleware',
]

so site wide cache and axes can not work at the same time :(

any possible workaround for this problem

thanks

[aleksihakli]

Would anyone have the opportunity to check the caching behavior with the site-wide cache and Axes cache enabled at the same time?