Arx, I am not sure how this is implemented but when I tried to make a HTTP request from my own machine I found that 8080 was not open (probably firewalled?).
I can understand the need to spam protect it but a HTTP server should answer from any location and reponsd with meaningful HTTP error codes.
Arx, I am not sure how this is implemented but when I tried to make a HTTP request from my own machine I found that 8080 was not open (probably firewalled?).
I can understand the need to spam protect it but a HTTP server should answer from any location and reponsd with meaningful HTTP error codes.
HTTP 429 seems an adequate one. Also a funny photo about it at https:/ /softwareengine ering.stackexch ange.com/ questions/ 128512/ suggested- http-rest- status- code-for- request- limit-reached
I think that the server should accept any requests regardless if it decides to drop them or send them.
Lets tune it for the moment and see what happens.
I created https:/ /review. openstack. org/622352 which should allow to track future recurrence of this error.