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 handshake: Unexpected response code: 502 #51

Open
raymondboswel opened this issue Nov 13, 2019 · 1 comment
Open

WebSocket handshake: Unexpected response code: 502 #51

raymondboswel opened this issue Nov 13, 2019 · 1 comment

Comments

@raymondboswel
Copy link

Hi,

I've managed to set up BLeak and added the mitm CA to my system. However, the wss connection to a third party system is failing with code 502. I suspect that the third party server is rejecting my certs as they have not added the mitm CA to their server. Is there a workaround for this, or would I have to get the third party to add the CA (at least in a QA environment)

@jvilk
Copy link
Member

jvilk commented Jan 3, 2020

Your intuition sounds correct, as I believe that MITMProxy will intercept websocket requests. I'm not sure if there's a way to prevent MITMProxy from intercepting websocket requests; you can check some of the options here:

https://docs.mitmproxy.org/stable/concepts-options/

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

No branches or pull requests

2 participants