Aapo Talvensaari
Aapo Talvensaari
@arezvani I meant about setting `router_flavor=traditional` as a workaround, can you test if it fixes your issue too? See: https://github.com/Kong/kong/issues/10758#issuecomment-1525457562 There seems to be an issue with `router_flavor=traditional_compatible` in `3.x`...
@arezvani can you share your Kong `KONG_STREAM_LISTEN` configuration?
@arezvani, is that `--port 30968` right, or should it be `--port 9443`?
@adcoutinho, can you try setting `router_flavor` to `traditional`: https://github.com/Kong/kong/blob/master/kong.conf.default#L1666 or with ENV variable: `KONG_ROUTER_FLAVOR=traditional kong restart`, and report back at us, if it helps.
I think the fix should be implemented here like you, @LeszekBlazewski, said: https://github.com/Kong/kong/blob/master/kong/init.lua#L1135-L1156
We, @kikito, @jschmid1, and @bungle, decided to move this to 3.4. This is a rather generic problem, and we would like to pursue different approaches before committing to this. Approaches...
Here is a draft of generic fix: https://github.com/Kong/kong/pull/10785
Moving this to 3.4, and perhaps abstract it a bit more.
> I'm all for fixing performance issues but I don't agree that this warrants a breaking change in Kong. As explained it is not only a performance fix, it also...
> If you are looking for a non-breaking compromise, you could always try to check the `Content-Length` header and only get the body if it is below a certain threshold......