Alejandro Martinez Ruiz

Hi @Anders429 @cuviper, I'm also looking for a way to test for features and perform additional tests with specific features enabled (ie. features for which an associated path was renamed...

> As a nitpick, I think having a single method called `with_features` that just enables the features for the span of the closure would be preferable to having separate `probe_with_features`...

was it? I see it not merged?

No, I didn't run into it. I just wanted to protect against the possibility that changes happen elsewhere and a new code path opens inadvertently that allows this to happen.

@googlebot I signed it!

Yes, this is a rewrite of #34 with a better user development experience and slightly nicer internal structure. So if we'll need typed constructors anyway it's not worth it to...

In the future there is a very good chance that the header values will require the use of [Structured Field Values](https://datatracker.ietf.org/doc/draft-ietf-httpbis-header-structure/) - so while a simple implementation using the draft...

When I think about rate limiting scoping I identify three potential sources of information: data attached to the request, data attached to the resource, and data attached to the environment...

It is very promising for replacing twemproxy when deploying multiple Redis instances. The very good thing I see is it appears to be actively maintained and aiming to support Redis...

@davidor we can repurpose this issue to test Envoy in a new deployment - and in particular to add support for Envoy as a proxy at the app level (ie....