-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add headers from the rlp call to the response #31
Conversation
It's panic'ing 😠 how to reproduce
❯ git diff
diff --git a/docker-compose.yaml b/docker-compose.yaml
index e0265d6..ced9f85 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -27,7 +27,7 @@ services:
- ./target/wasm32-unknown-unknown/release/wasm_shim.wasm:/opt/kuadrant/wasm/wasm_shim.wasm
limitador:
image: quay.io/kuadrant/limitador:latest
- command: ["limitador-server", "-vvv", "/opt/kuadrant/limits/limits.yaml"]
+ command: ["limitador-server", "--rate-limit-headers", "DRAFT_VERSION_03", "-vvv", "/opt/kuadrant/limits/limits.yaml"]
expose:
- "8080"
- "8081"
It is raising uncaught runtime error when adding the response headers. Specifically when calling |
Thanks @eguzki ! Sorry about this, let me investigate this... |
bb50371
to
4c5a176
Compare
4c5a176
to
0962430
Compare
With @eguzki steps above, we now get the headers in the response in both cases, 200s & 429s:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: instead of headers
, which is too generic, why not call it response_headers_to_add
? I am sure you can come up with a better name :)
working in my local host. 🎖️ |
Slightly renamed fields where it made sense. The headers, where they are added, are matched from the destructuring of |
Duh, now I understand what you meant: #33 |
See Kuadrant/limitador#158