Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

websocket - gzip/deflate TextWebSocketFrame through Proxy is not getting decompressed before consumed #1689

Closed
zhp0260 opened this issue Jan 7, 2020 · 1 comment
Assignees
Labels
Milestone

Comments

@zhp0260
Copy link

zhp0260 commented Jan 7, 2020

I have a situation :
Websocket ----> (proxy app:AsyncHttpClient) ----> Proxy ----> Origin Server( web site)
Ex: URL: wss://pshudws.365pushodds.com/zap/?uid=1234567890

While I can get the websocket message correctly when accessed without Proxy; the app shows (junk) gzip data when accessed the same pages through Proxy.

My proxy configuration doesn't unpack the gzip/deflate TextWebSocketFrame received from Origin. I think the AsyncHttpClient should decompress it, before the response is consumed downstream.

I read the source, I find websocket connect without proxy, use wsBootstrap object to handle it, when use proxy, use the httpBootstrap object to handle it.

Could you please look into it, or suggest any workaround. Please let me know if you need more information.

thanks,
1578360160(1)

@slandelle slandelle self-assigned this Jan 7, 2020
@slandelle slandelle added this to the 2.11.0 milestone Jan 7, 2020
@slandelle
Copy link
Contributor

Thanks for reporting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants