This is the output:


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

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).