-
Notifications
You must be signed in to change notification settings - Fork 384
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
Handle new action "OPEN_TUNNEL" #108
Comments
The initial fix doesn't seem to hard. It appears to return the same data as the url in "HTTP_REQUEST" which looks like this
The big question is what does the server expect to see?
With OPEN_TUNNEL the server could be expecting something different |
Yeah i tried to debug on extensions but seem they dont return OPEN TUNNEL for extensions, so basically be careful. Only way to know is debug the desktop app it-self |
Yeah and that is hard. The app has SSL pining and I'm not knowledgeable enough to know how to remove it |
Haven't found a solution to the problem yet? |
I tried to capture the package, but the desktop could not find the websocket package |
Can somebody make push request that I add it to bot? |
Haven't found a solution to the problem yet? Still waiting for it. |
They just present new action to the websocket call OPEN_TUNNEL.
This also make the script crashing with exception include "method" this is because the request_data does not contain the method any more.
I think that they change the regular HTTP_REQUEST action into another tunnel connection.
`09:47:24.46 INFO 1 | Connected
{'id': 'KJI2JJLFCroN6NpFXfhDr', 'action': 'OPEN_TUNNEL', 'data': {'url': 'https://api.getgrass.io/somethign/something'}}
{'url': 'https://api.getgrass.io/something/something'}
The text was updated successfully, but these errors were encountered: