uninitialized sanitized_request

is it something faulty configuration more time

this lines apear with bad encoding

uninitialized sanitized_request variable while login request
is it normal or something might be problem ?

2020/03/19 22:20:17 [warn] 32101#0: *40 using uninitialized "sanitized_request" variable while logging request, client: 123.192,29.24, server:mydomain, request: "?ן???? ?8:??<?P??%?M?? 1?pG:<???????P????u}!n?z$?+?/̨̩?,?0?"
[nginz] 192.168.100.4 - - [19/Mar/2020:22:20:17 +0100] "" 400 150 "-" "-" "-" - 40 0.192 - - - - 6ea89d46fbd74ee14e29c5dd046ac7b0
[nginz] 192.168.100.4 - - [19/Mar/2020:22:20:17 +0100] "OPTIONS /self HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" "-" - 11 0.000 - - - - 75e43af7e10477f580a4bfded7f3d8b5
[nginz] 192.168.100.4 - - [19/Mar/2020:22:20:17 +0100] "GET /self HTTP/1.1" 200 295 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0" "-" - 29 0.021 0.024 - a6e6c7fe-0dbc-42c0-95b7-f67326647d49 13343654931964971856 4387cdb115e40a54fd8bcc9c0d0af319

Start by tracing the nginx/nginz request-logging configuration that defines sanitized_request and reproduce the warning with the malformed-encoding login request shown. Done means establishing whether the warning is expected and, if it is a defect, identifying the relevant configuration or code change and a regression check.