Concurrent rate limit to send 429 http status by using a property

Not applicable

In the apigee documentation, i see we can set a property features.isHTTPStatusTooManyRequestEnabled to send 429 status instead of 503 error when the concurrent rate limit is reached.

http://docs.apigee.com/api-services/content/comparing-quota-spike-arrest-and-concurrent-rate-limit-p...

1. How to set the property ?

2. Is this applicable for all versions of apigee ?

3. Is this per organization ? Does 429 status applicable only for concurrent rate limit proxy?

Or 429 will be sent irrespective of concurrent rate limit and for other use cases as well ?

1 3 355
3 REPLIES 3

More details here: https://community.apigee.com/questions/3606/how-to-set-ishttpstatustoomanyrequestenabled-to-re.html

Apigee-hosted customers need to contact Support to set the property. OPDK customers can set it themselves (see link above).

Applicable for all recent versions. I think it came in 2015.

It's per org, applies to other use cases as well (spike arrest, e.g.)

Could you please provide the contact info to set the property on apigee-hosted.

I have created a local set up, https://enterprise.apigee.com/platform/knhemanth/

so I need to contact apigee support team right ?

I would like to try out locally first and then do the on premises set up.

Here's the link to the support portal: https://apigee.com/about/support/portal

That's where you request to make the change for the hosted org. The opdk version the linked side should cover it, but you can also contact support if you run into trouble.