root@hack3rs:/srv/www$ curl -i /400/
HTTP/1.1 400 Bad Request
The server could not process the request as sent.
status-summary.log
HTTP 400 Bad Request
This usually means the request format, headers, or parameters were malformed, incomplete, or incompatible with what the endpoint expects.
Validate request syntax, encoding, content type, and required fields before retrying.
likely-causes.lst
- $Malformed URL, query string, or request body.
- $Missing required headers such as Content-Type or Authorization.
- $JSON or form payload parsing failed on the server.
- $Reverse proxy or WAF rejected a non-compliant request.
recovery-steps.md
- Recreate the request with known-good input.
- Check API documentation for required headers and field names.
- Validate JSON syntax and character encoding (UTF-8).
- Review server or proxy logs for parser errors and rejection reasons.
quick-actions.sh
ops-note.txt
Use these pages for debugging and user guidance. In production, configure your host or reverse proxy to return the matching HTTP status code for the route (especially for 400 and 404/500 responses) rather than serving a 200 with error-themed content.