"add-response-headers" property does not seem to be working
See original GitHub issueThe ratelimit headers do get added to the response by default, but when i try to remove them using the “add-response-headers” property they are still in the response.
If you are using Spring Boot version 1.5.x you MUST use Spring Cloud Zuul RateLimit version 1.7.x.
I picked up on this, so i am using ratelimit version 1.7.3.RELEASE
my current config looks like this.
ratelimit:
enabled: true
add-response-headers: false
repository: JPA
policy-list:
service-x:
- limit: 60
refresh-interval: 10
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Add response headers doesn't seem to work #269 - GitHub
running core tools 2.7.1373 on macOS and published on Azure Function App When trying to add response headers, they do not get appended ......
Read more >asp.net Core Add Response Headers in Middleware after ...
If I register my middleware before UseRouting , the header is added as expected, but if it comes after, it executes, but the...
Read more >Spring Cloud Gateway
This project provides an API Gateway built on top of the Spring Ecosystem, including: Spring 5, Spring Boot 2 and Project Reactor. Spring...
Read more >Add response headers | Edge Stack
When it is an object , the object should have a value property, which is the actual header value, and the remaining attributes...
Read more >InvokeHTTP - Apache NiFi
Display Name API Name Default Value
HTTP Method HTTP Method GET
HTTP URL Remote URL
HTTP/2 Disabled disable‑http2 False
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @devc0n thanks for your finding! I just checked it out and it indeed is a bug, actually, the feature is only present in the
2.x
series.I’ll sync it to the
1.7.x
as well.@devc0n it took longer than I expected but I finally managed to fix and deploy to maven central the version
1.7.5.RELEASE
.