Gil Pedersen

Thanks, but I asked you to create an issue, not just say the same thing again. In order to fix this, we need a lot of more details, and preferably...

Thanks, this helps a bit. From what you describe, it is an issue that can happen under extreme load. I would still like some more insight into the server config...

Yes, this is probably a substantial change. If we look into this, we could also consider supporting something like protobuf, where some kind of schema is needed to parse it.

The payload parsing could definitely do with a rework, and making it pluggable seems very reasonable. I'm not sure that your specific suggestion works that well though. We can't really...

@SK-FComputer Yes, I think that you are spamming, posting this 3 places. Just post once, and link it from other issues. Also, it's quite rude to @ people for an...

It seems that you found a minor bug. Unknown content-types are documented to return a 400 Bad Request response here: https://hapi.dev/api?v=20.2.0#-routeoptionspayloadparse - but really a 415 response is returned. I...

I am looking into this as part of an upcoming PR that revises some of the stream transmit logic. During my refactor I was encountering issues around aborted requests, and...

This will still break this specific Chrome support, since it most likely polyfills the internal `ReadableStream` using the `readable-stream` module, which is outdated and does not expose all modern APIs....

I think it would make sense to limit the accepted methods in the route definition to any that node can handle. Unfortunately there is no way to fetch this list...

I agree that this is a bit confusing compared to the `response` event, which occurs at a fixed point. The `request` event is not a single event, but a *channel*,...