Enrique García Cota

The way the request transformer is set up, `remove` is the "strongest" constraint (it gets applied the last). So if you set the headers to `remove` they will always be...

Hello, thank you for sending this PR. It touches a lot of things so it might take us a while to review it, but I wanted you to know that...

Hello @seh , I was looking at this issue (for which you have done a very good job at analyzing that the problem) and realized that you are using Kong...

Thanks for the report and the analysis, @evertvanaart! I gave this a very quick look and it looks like a typo, the correct value should be `KONG_HEADER_FILTER_START` - a simple...

Hello, there's several key important points on this issue: @AndyEWang: > Kong 0.12.3 > I'm afraid that no upgrades are planned in the near future. We don't have the bandwidth...

> Is there a way we can avoid this issue? Not completely, by design. Two geographically disperse are eventually consistent by nature. The tokens being on the replica immediately after...

I just noticed I had not answered this part of your ticket: > TPS is reduced to 1/3. OAuth call throughput reduction is expected because of delay but why other...

> 2.5 That version of Kong is getting older, you might be hitting an already-resolved bug. > 500k consumers That is a high number of consumers to start with. Does...

Kong will not run plugins associated to a particular Service or Route if the requests received don't correspond to those Services or Routes. Usually that is a desirable behavior. Is...

While we get this (or other) solution merged into rickshaw, here's a dirty hack to update the whole series - keep using the same `series`, and replace each element with...