Tim Düsterhus

> Running haproxy using haproxy:2.2.14 docker image. You should use a newer version. 2.2.14 is 1.5 years old and affected by 290 fixed bugs: https://www.haproxy.org/bugs/bugs-2.2.14.html > The expected behaviour is...

> Any idea what we need to do in the build in order to enable this? (Missing dependencies, build configuration, etc.) https://github.com/haproxy/haproxy/blob/63fc900ba282437b96868103f1eb7db9ee7f482c/INSTALL#L395-L417

I do not understand this issue. What is the problem? The `hydra` design is working just fine for me and is included with the Docker Image. 

> I don't know if this is actively developed, Not actively *developed*, because I consider this to be feature complete, I'll however try to respond to issues and to fix...

> It would be nice to have a uniq id logged by default for debugging and tracing through all levels. I agree with that. I configure `unique-id-header` everywhere, but always...

> Patches are welcome to add new options While implementing a desired feature yourself in many cases is the fastest way to get the feature, not everyone is capable of...

> We were able to collect a core dump (9,6GB). We've shared it here, but please let us know when you download it so we can take it offline: You...

The proposed implementation allows for cache poisoning, because it's trivial to find crc32 collisions. In contrast to the “Referer” header collisions on “Origin” will actually be harmful, because the client...

> Caching thru disk by default is not expected by a HTTP library. [citation needed]

Oh, this only exists as of PHP 7.3. Would you consider it appropriate to drop support for PHP 7.2? It's at 1.8% for Guzzle 7 as per: https://packagist.org/packages/guzzlehttp/guzzle/php-stats#7