code
code
> It looks like the get functions handle multiple values: https://github.com/envoyproxy/envoy/blob/c58b4eaab93cdc13a786c246dd75cdb26b7a7ce0/source/extensions/filters/http/lua/wrappers.cc#L43-L65 > > So I think for the iterator we just also need to support the all values version? yeah,...
And I just find a new bug. 🤣 The get functions not handled the cookie header correctly. The `,` will be used as separator.
I personally like to create a table of tables. And will have a try.
Closed by #22871
Could you provide some more detailed description of `inside the server` and `inside the container`? Does `inside the container` mean that running bench client in the server's container directly? 100ms...
May be a linux `perf`? Please make sure that a non-stripped envoy binary is used. If you have a build farm for envoy, you can also rebuild envoy with `gperftools`....
From the output of top, the envoy is not the bottleneck obviously.
20ms is also big variation for just moving the client from container to server. By the way, which HTTP protocol is used in your test? If the long connection is...