Zsolt Imre

The way we mitigated it (`canRead: ['.yml', '.json']` mentioned above) works perfectly fine for us, given there are no other `yml` or `json` documents with sensitive info around, just the...

The related pull request: https://github.com/APIDevTools/swagger-parser/pull/236

Just had a look into this. I found traces of the problem from 2004 and indeed, `curl` had some workaround implemented such as `Z_SYNC_FLUSH`. But, on top of that, from...

@jeremy-daley-kr It's been a while since I had a look into this so I did another round of testing again and was playing around with the `Content-Encoding` and the body...

@jeremy-daley-kr You don't think or do you know for sure? The reason why I asked for your node version and the version of `koa-better-http-proxy` you are using is that even...

Update. While I'm still unable to reproduce with **HEAD** requests, I could reproduce with a **GET** request. So, a raw HTTP response example to a GET request that could trigger...

@jeremy-daley-kr I was also looking into it as the tests needed some changes to work as expected. Anyway, as things are not moving with this project, I applied the fix...

I can confirm the above. My fuzzer triggered the issue in less than 1800 requests.