Update Django-Security to support Django 5.2 (#134)

* Fixed some broken behaviour with middlewares that caused issues under
  5.2
* Update version support for Django
* bump version to 5.1.6

Co-authored-by: Emily Bain <ebain@securitycompass.com>

Author: emily-bain

poetry.lock

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "django-security"
-version = "1.1.5"
+version = "1.1.6"
 homepage = "https://github.com/sdelements/django-security"
 description = "Models, views, middlewares and forms to facilitate security hardening of Django applications."
 authors = ["Security Compass <contact@securitycompass.com>"]
@@ -39,7 +39,7 @@ exclude = [
 
 [tool.poetry.dependencies]
 python = "~3.12"
-django = "~4.2"
+django = ">=4.2, <6.0"
 python-dateutil = "2.9.0.post0"
 south = "1.0.2"
 ua_parser = "0.18.0"

pyproject.toml

@@ -105,7 +105,7 @@ def _on_setting_changed(self, sender, setting, value, **kwargs):
             self.load_setting(setting, value)
 
     def __init__(self, get_response=None):
-        self.get_response = get_response
+        super().__init__(get_response)
 
         if not self.REQUIRED_SETTINGS and not self.OPTIONAL_SETTINGS:
             return
@@ -701,7 +701,7 @@ def _csp_builder(self, csp_dict):
 
     def __init__(self, get_response=None):
         # sanity checks
-        self.get_response = get_response
+        super().__init__(get_response=get_response)
 
         conf_csp_mode = getattr(django.conf.settings, "CSP_MODE", None)
         self._csp_mode = conf_csp_mode or "enforce"