Alexander Emelin

@PhilipDukhov thanks! I remember about this – just a bit busy with other tasks these days. Will switch back soon.

> I suggested following approach to avoid hard dependency My concern was that centrifuge-java won't be able to switch from OKHttp or migrate to another version of OKHttp in that...

> PS: I looked through the tarantool-centrifuge code. It uses session.push as a data stream, so it is an example of OOM problem. If tarantool has too many slow clients,...

I'd also like to mention the real-life use case of `box.session.push` we have - https://centrifugal.dev/blog/2023/08/29/using-centrifugo-in-rabbitx. Nine months in production with zero issues. So I'd like to ask once again -...

> Sorry, but it isn't possible. We analysed the problem and found that it's impossible without protocol modifications. The problem can be moved from server to client, but can not...

Hey @ghstahl , I do not see why token with channels should allow getting history. It subscribes connection to channel using server-side subscription, but there is nothing about history permission....

They are not the same, as I said previously `caps` claim is about permissions, `channels` claim is about telling Centrifugo to subscribe connection to specified channels using server side subscriptions....

`allow_history_for_subscriber ` on top level corresponds to top-level namespace - for all channels without `:` separator. [Channel namespaces](https://centrifugal.dev/docs/server/channels#channel-namespaces) and [Channel config examples](https://centrifugal.dev/docs/server/channels#channel-config-examples) show this.

👍 If I understood correctly the above – works as expected, closing.

Hello @richelieu-yang How did you enable GZIP? Share the entire configuration of Centrifugo and your proxy, steps to reproduce