http / HTTP
HTTP 400: Bad Request
The server cannot or will not process the request because of something perceived as a client error, such as malformed request syntax.
Visible symptoms
- HTTP status 400.
- Status text: Bad Request.
Safe verification and recovery
Check the request
Review the request syntax, headers and body, then resend a corrected request.
Matching evidence and limitations
Reported error signals
Matches the documented error signal; it identifies the documented case, not the exact root cause of your request.
The local analyzer never executes suggested commands or treats a possible match as certainty.