Nginx has actually no support for the 429 code. Either you fix it by
proposing a patch to support the error page in core or you use an
error_page directive.
error_page 429 @toomany;
location @toomany {
return 429 'Too many requests.\n';
}
Just a simple example.
Le 28 oct.
Hi Francis,
Probably I shouldn't have said "malformed" when I chose a word to express
the problem with the response. But I assumed that Nginx should show the
phrase that corresponds to the code. I assumed that Nginx has been coded so
it know that 429 means "Too Many Requests" and that we should re
ly is a hard requirement and cannot be omitted.
It can't be omitted, but it can be zero-length. The SP before it looks
to be the part that shouldn't be omitted.
It looks like a straightforward fix:
diff -pru nginx-1.4.3/src/http/ngx_http_header_filter_module.c
nginx-1.4.3-wip/src/http/n
url
fails to parse this bogus HTTP response (maybe you are using different
curl releases).
If we look again at Brian's curl output, we don't see any Server header
in the response, which is not configurable in nginx afaik:
< HTTP/1.1 429 nginx/1.4.3 <--- THIS IS WRONG
< Da
On Sun, Oct 27, 2013 at 09:40:11AM -0400, Brian08275660 wrote:
Hi there,
> I think I'm actually reporting a malformed response, it is Nginx that send
> "nginx/1.4.3" instead of something useful as "too many requests".
This is quite confusing to me.
What you hav
.0 OpenSSL/1.0.1
zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: api..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: ke
On 27 October 2013 13:40, Brian08275660 wrote:
> I think I'm actually reporting a malformed response, it is Nginx that send
> "nginx/1.4.3" instead of something useful as "too many requests".
Please show the complete output of "curl -v <429-uri>".
Hi Francis,
I think I'm actually reporting a malformed response, it is Nginx that send
"nginx/1.4.3" instead of something useful as "too many requests". I have
tested it with Firefox and there is no doubt. Also tested it with a java
HTTP client component, the same result.
On Sat, Oct 26, 2013 at 11:43:29PM -0400, Brian08275660 wrote:
Hi there,
> The module HttpLimitReqModule delivers "nginx/1.4.3" (at least with version
> 1.4.3) as a message for the HTTP status code 429. That is too generic and
> not useful at all.
Are you reporting tha
Hi,
I'm doing this: limit_req_status 429;
The module HttpLimitReqModule delivers "nginx/1.4.3" (at least with version
1.4.3) as a message for the HTTP status code 429. That is too generic and
not useful at all. Why doesn't it deliver a "Too Many Requests" message
Hello Nginx users,
Now available: Nginx 1.4.3 for Windows http://goo.gl/vjluLA (32-bit and
64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.
Announcements are also
Wow, that's maintenance ^^
Thanks to the dev team.
I am getting lost on the trac Web interface: where could I get details o
nthe defect affecting autoindex?
I'll wait for the Debian package to be available in the repo, then... :o)
---
*B. R.*
___
ngi
Changes with nginx 1.4.3 08 Oct 2013
*) Bugfix: a segmentation fault might occur in a worker process if the
ngx_http_spdy_module was used with the "client_body_in_file_only"
directive.
*) Bugfix: a segmentation fault migh
13 matches
Mail list logo
