[REG: 5.15.8->5.15.9]: When a 401 code is issued then it is passed to the application which can cause a loop and eventually fail with a 200 code

When the an account is locked out, the following is shown in Fiddler:

HTTP/1.1 401 Unauthorized
Content-Type: text/html
Server: Microsoft-IIS/10.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM
X-Powered-By: ASP.NET
Date: Wed, 04 Jan 2023 05:04:55 GMT
Content-Length: 1293
Proxy-Support: Session-Based-Authentication

NetworkRequest will receive the 401 error and will pass it onto app and app will reattempt in a loop. In normal circumstances, the 401 is absorbed by Qt and should never be shown to app. Instead, Qt may retry silently and, eventually return a 200 with a valid response from the server. This pattern is consistent with Chrome.

This happened as a result of 78ed4a4856a5373ed1222d52f71a0b59635807b3 which was fixing QTBUG-44096.