zed icon indicating copy to clipboard operation
zed copied to clipboard

Read HTTP proxy from env

Open dylankyc opened this issue 1 year ago • 4 comments

This PR will use http proxy from env for downloading files.

dylankyc avatar Jan 26 '24 11:01 dylankyc

We require contributors to sign our Contributor License Agreement, and we don't have @lichuan6 on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'.

cla-bot[bot] avatar Jan 26 '24 11:01 cla-bot[bot]

@cla-bot check

dylankyc avatar Jan 26 '24 11:01 dylankyc

The cla-bot has been summoned, and re-checked this pull request!

cla-bot[bot] avatar Jan 26 '24 11:01 cla-bot[bot]

@lichuan6 Thanks for this!

I think we should configure the proxy on the HTTP client, instead of on get requests. This will ensure it is used for everything (including post_json automatically).

In the environment you're working in, do web sockets work correctly? I don't think we can try and establish the web socket connection through an http proxy, but I am curious if we need to do anything to make them work too.

ConradIrwin avatar Jan 26 '24 17:01 ConradIrwin

@ConradIrwin

I've configured the proxy on the HTTP client, instead of on get or post_json methods.

As for web sockets through http proxy, is there a way to verify if WebSocket communication works through an HTTP proxy?

Thanks

dylankyc avatar Jan 29 '24 04:01 dylankyc

@lichuan6 in development builds, if you click on the sign in button on the top right, sign into our service via github or keychain, and then open the collab panel on the bottom right, you should be able to test it. If you're able to make new channels and such in that UI, then you're good. The collaboration features all use websockets.

mikayla-maki avatar Jan 30 '24 01:01 mikayla-maki

Hi @mikayla-maki I tried to sign in on the top right, however, I failed with the following error. Screenshot 2024-01-30 at 21 51 50

Any idea how to fix it?

dylankyc avatar Jan 30 '24 14:01 dylankyc

Try rebasing your branch :) we recently updated our protocol pretty significantly, and we're only able to with the latest version of the protocol.

mikayla-maki avatar Jan 30 '24 18:01 mikayla-maki

Thanks for this, and sorry for all the back and forth here!

ConradIrwin avatar Feb 01 '24 03:02 ConradIrwin