Brandon

Bump. I'd like to see a fix for this as well

Bump. By default hackney can only make [50](https://github.com/benoitc/hackney/blob/362f062794342c1a29cd70cdabc808b0ab02afa1/src/hackney.app.src#L23) requests before it blocks completely.

That is to say this is a non-starter since we only get to 51 ```erlang lists:foreach(fun(I) -> timer:sleep(500), io:format("req ~p~n",[I]), hackney:get("https://google.com") end, lists:seq(1, 100)). ```

The issue is present for `post` (and presumably `put`) as well which is how we originally discovered it

@benoitc do you consider the default `get` behavior a bug? Not all GETs have a body (e.g. on a 304)

I'm eagerly awaiting this merge. Any movement on this?

Forgot to mention: you might think it's better to aggregate FQDNs by cert _content_ (i.e. a digest), or inspect the cert and aggregate by Common Name. The latter was our...

Is this the cause of the N^2 behavior we're seeing on EDS updates? For every EDS `DiscoveryRequest` we're pretty sure the entire EDS config is being sent back

EDS is the only xDS that will benefit from this right? It feels like #1166 and #1172 but with a bit different description. Also, I'd still appreciate a response to...

From the Envoy docs: > It’s challenging to provide the above guarantees on sequencing to avoid traffic drop when management servers are distributed Challenging but not impossible. Also, we're running...