Stephane Landelle

I suspect AHC 2.1 will only support multiplexing, like OkHttp, ie no API change and no push.

@scyiwei By "we", do you mean you plan on contributing?

We've started working on HTTP/2 internally. Work with first be pushed in FrontLine, our Gatling Entreprise product, then Gatling. We'll port into AHC once we are confident with providing a...

@lpandzic Not on my side. I won't be working actively on this project anymore, just coordinating contributions. I've moved Gatling to [its own HTTP client](https://github.com/gatling/gatling/tree/master/gatling-http-client/src) so I can change things...

For sure, I'll never have the bandwidth on my own personal time to work on this. Feel free to contribute.

Please try to trim your reproducer to AHC only, eg one hitting a public website (eg google.com). I can't investigate such complex sample that mixing lots of different technologies. Your...

This "just" is already too much. For example, your problem could be wiremock not being able to server more than 1 request at a time. Please kick out everything that's...

Contributions welcome. That's not something I expect to work on any time soon.

This bug is not a priority for me, as I don't use ResponseFilters in Gatling. It would be great if you could contribute a fix.

To be frank, I think that those RequestFilters/ResponseFilters/IOExceptionFilters are more or less broken. They were introduced before I joined here, their test coverage is not sufficient in regards to the...