HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

Brian08275660 nginx-forum at
Sun Oct 27 17:22:06 UTC 2013

This is the output:

root at ip-10-139-33-71:~# curl -v <URL was here >
* About to connect() to port 80 (#0)
*   Trying connected
> GET /location/locate-ip?key=BBANBWEDS7UZ6FD8747F76VZ&ip=
> User-Agent: curl/7.22.0 (i686-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1
zlib/ libidn/1.23 librtmp/2.3
> Host:
> Accept: */*
< HTTP/1.1 429 nginx/1.4.3  <-----------------------------------------THIS
< Date: Sun, 27 Oct 2013 17:12:42 GMT
< Content-Length: 0
< Connection: keep-alive
* Connection #0 to host left intact
* Closing connection #0
root at ip-10-139-33-71:~#

Please look the line I'm considering wrong. After "429" it says
"nginx/1.4.3", whereas it shoud say "too many connections" or something like

The HTML output is empty, certainly. I can customize that with the
"error_page" directive so that not a big problem (even though I think it
should deliver a standard non-empty response explaning the 429 code).

Posted at Nginx Forum:,244156,244169#msg-244169

More information about the nginx mailing list