Fix unhandled exception when resolver_match returns None
In some cases (e.g. in the clinerion service) resolver_match
returns None
, which causes an unhandled exception when app_name
attribute is accessed. Investigate in which situations the value can be None
. If None
is a valid value provide a sensible default to avoid the exception.
More logs are available at ELK (from:'2021-07-16T12:30:00.000Z' to:'2021-07-16T13:00:00.000Z')
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/django/core/handlers/exception.py", line 47, in inner
response = get_response(request)
File "/usr/local/lib/python3.8/site-packages/django_detailed_request_logging/middleware.py", line 48, in __call__
self.process_request(request, response)
File "/usr/local/lib/python3.8/site-packages/django_detailed_request_logging/middleware.py", line 72, in process_request
self._log_request(request, response)
File "/usr/local/lib/python3.8/site-packages/django_detailed_request_logging/middleware.py", line 138, in _log_request
"app": request.resolver_match.app_name,
AttributeError: 'NoneType' object has no attribute 'app_name'