BestHub
Sign in
Tagged articles

400-bad-request

2 articles · Page 1 of 1
ITPUB
ITPUB
Jun 10, 2026 · Operations

Avoidable P1 Outage: How Nginx Changes Caused All Gateway Requests to Return 400

A production change replaced two Nginx reverse‑proxy servers, introduced an upstream name containing an underscore, broke the Host header required by HTTP/1.1, and caused Spring Cloud Gateway to return 400 Bad Request for every request until the configuration was corrected.

400-bad-requestHTTPNginx
0 likes · 16 min read
Avoidable P1 Outage: How Nginx Changes Caused All Gateway Requests to Return 400
dbaplus Community
dbaplus Community
Mar 22, 2017 · Operations

Why Nginx Returns 400 Bad Request and How to Fix It

This article walks through a real‑world Nginx 400 Bad Request incident, explaining how missing or malformed Host headers and added proxy headers caused the error, and provides step‑by‑step diagnostics, configuration comparisons, and the final fix of using the correct $host variable.

400-bad-requestNginxhost-header
0 likes · 13 min read
Why Nginx Returns 400 Bad Request and How to Fix It