Welcome! Log In Create A New Profile

Re: [PATCH 2 of 3] Upstream: allow recovery from "429 Too Many Requests" response

Forum List Message List New Topic Print View

Piotr Sikora via nginx-devel

March 01, 2017 03:18PM

Hi Maxim,

> Not sure it's good idea to don't count a 429 response as a peer
> failure. Contrary, counting it as a failure will naturally reduce
> load on the particular server, resulting in less rejects.

But 429 can be returned on a per request basis (think client IP
exceeding limit_req limits, or a logged in user that's rate-limited
based on API usage), so I'd question marking backends as failed
because of that.

Best regards,
Piotr Sikora
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel

Reply Quote

RSS

Subject	Author	Views	Posted
[PATCH 1 of 2] HTTP: add support for "429 Too Many Requests" response (RFC6585)	Piotr Sikora	988	October 19, 2016 03:54AM
[PATCH 2 of 2] HTTP: change default response code when rate-limiting requests	Piotr Sikora	302	October 19, 2016 03:54AM
Re: [PATCH 1 of 2] HTTP: add support for "429 Too Many Requests" response (RFC6585)	Piotr Sikora via nginx-devel	286	November 29, 2016 08:10PM
Re: [PATCH 1 of 2] HTTP: add support for "429 Too Many Requests" response (RFC6585)	Piotr Sikora via nginx-devel	380	January 20, 2017 08:04PM
Re: [PATCH 1 of 2] HTTP: add support for "429 Too Many Requests" response (RFC6585)	Piotr Sikora via nginx-devel	231	February 22, 2017 10:40PM
Re: [PATCH 1 of 2] HTTP: add support for "429 Too Many Requests" response (RFC6585)	Maxim Dounin	237	February 25, 2017 06:46PM
[PATCH 1 of 3] HTTP: add support for "429 Too Many Requests" response (RFC6585)	Piotr Sikora via nginx-devel	586	February 28, 2017 06:42PM
[PATCH 2 of 3] Upstream: allow recovery from "429 Too Many Requests" response	Piotr Sikora via nginx-devel	287	February 28, 2017 06:42PM
Re: [PATCH 2 of 3] Upstream: allow recovery from "429 Too Many Requests" response	Maxim Dounin	231	March 01, 2017 10:34AM
Re: [PATCH 2 of 3] Upstream: allow recovery from "429 Too Many Requests" response	Piotr Sikora via nginx-devel	225	March 01, 2017 03:18PM
Re: [PATCH 2 of 3] Upstream: allow recovery from "429 Too Many Requests" response	Maxim Dounin	241	March 01, 2017 07:00PM
Re: [PATCH 2 of 3] Upstream: allow recovery from "429 Too Many Requests" response	Piotr Sikora via nginx-devel	239	March 24, 2017 06:50AM
[PATCH 3 of 3] Limit req: change default response code when rate-limiting	Piotr Sikora via nginx-devel	218	February 28, 2017 06:42PM
Re: [PATCH 3 of 3] Limit req: change default response code when rate-limiting	Maxim Dounin	226	March 01, 2017 10:40AM
Re: [PATCH 3 of 3] Limit req: change default response code when rate-limiting	Piotr Sikora via nginx-devel	217	March 01, 2017 03:22PM
Re: [PATCH 3 of 3] Limit req: change default response code when rate-limiting	Maxim Dounin	252	March 01, 2017 07:18PM

Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 302

Record Number of Users: 8 on April 13, 2023

Record Number of Guests: 421 on December 02, 2018