| Event Id | 52 |
| Source | Microsoft-Windows-HttpEvent |
| Description | Parsing of request (request ID %2) failed due to reason: %3. Request may not be compliant with HTTP/1.1. |
| Event Information | According to Microsoft : Cause This event is logged when parsing of request failed due to reason.Request may not be compliant with HTTP/1.1. Resolution Modify client application to be compliant with HTTP/1.1 With a parsing failure, the client application might not be sending an HTTP/1.1-compliant HTTP request. For example, a parsing failure might result from a client application sending an HTTP request that lacks a HostHeader. The client application should be modified to send a compliant HTTP request. Verify If parsing has failed because of a 4xx error, there will be a ParseRequestFailed error in your HTTPERR log at the following directory: %Windir%\System32\Logfiles\HTTPERR If there is no ParseRequestFailed error present, the parser has not failed. |
| Reference Links | Event ID 52 from Source Microsoft-Windows-HttpEvent |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.