Comments (7)
This is a duplicate of #368
from apicast.
I am all for improving this, but I would prefer to take a bit more time and do a proper implementation with the ability to customize the response. The code to handle that was designed in a good extensible manner. The second phase beyond that would be to provide meta data response to the client about the rate limit and the time remaining until the next window.
from apicast.
I agree we can wait. Especially as it seems we can use the X-3scale
header that will be supported according to @unleashed. This should cover most scenarios in the meantime.
from apicast.
OK.
Will the X-3scale be documented in the trouble-shooting guide. I see this behavior as a trouble-shooting problem for providers....
from apicast.
Once it is supported and documented it makes sense to document it also in the troubleshooting guide.
from apicast.
The response header referred by @kevprice83 would be (with the corresponding value):
3scale-rejection-reason: limits_exceeded
For this to work the gateway will need to provide a header in its request to backend with the following form:
3scale-options: rejection_reason_header=1
and if it not parsing the body, use instead:
3scale-options: no_body=1&rejection_reason_header=1
This needs to wait until deployment of the affected backend version, which we are working towards completing today (or given the current time, probably on Monday).
from apicast.
Just chipping it to say that the deployment of support for that header happened a while ago.
from apicast.
Related Issues (20)
- backend.t HOT 1
- resolver.t HOT 2
- balancer.t HOT 1
- apicast-upstream-balancer.t
- management.t
- apicast-mapping-rules.t
- backend-cache-handler.t
- Review and update DNS-resolver doc HOT 5
- Setup local env fails HOT 13
- Retiring the probot-changelog app HOT 1
- Trigger Alert `CoreDNSErrorsHigh` with OpenShift 4.11.9 HOT 2
- Swagger compatibility Issue HOT 5
- Edge Limiting is sharing the hits across windows HOT 3
- GRPC integration tests HOT 1
- OpenTelemetry instrumentation does not use environment variable OTEL_RESOURCE_ATTRIBUTES HOT 1
- Need help with build failure on power HOT 2
- lua-rover issue faced while enabling support for power(ppc64le) architecture HOT 4
- Immediate, infinite recursion when configuration loader is set to `boot` and reloading is disabled HOT 2
- Keycloak roles and services under roles HOT 1
- Make prove command failing while enabling support for power(ppc64le) architecture. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from apicast.