David Ortiz
David Ortiz
OK. So let's leave this out for 3.3, but keep the issue open for future consideration. If someone experiences a performance problem related with this, please let us know.
The "matches" operation was added in #975
Now it is @unleashed :D
We should also consider operations such as "includes" and "excludes" as suggested by @mikz in https://github.com/3scale/apicast/pull/976#discussion_r247752113
I started a WIP branch to modify the rate limit schema and make it compatible with the `react-jsonschema-form` library: https://github.com/3scale/apicast/tree/adapt-rate-limit-policy-schema-to-react-jsonschema I still need to modify the code and the tests...
The schema of the rate-limit policy was modified in https://github.com/3scale/apicast/pull/696 The issue of introducing an automated way of validating the schemas to make sure they're compatible with `react-jsonschema-form` remains open.
The code always compares what's in `match.uri_path` with the request path using `==`. @jmprusi , @mikz Should we always interpret `match.uri_path` as a regex and check if it matches the...
Answers inline: > Problems: > > * Support for `SUNION`. Is there a fundamental reason it is not implemented? Doing it in the app is `bad`. > To use `SUNION`...
I just realized that we are using "fnv1a_64" as the hash function in Twemproxy, and Envoy does not use that one : https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/cluster.proto#enum-cluster-ringhashlbconfig-hashfunction So, while starting a new installation with...
Yes, that's it.