You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all!
It is not possible to adapt the work of your asynchronous part of the library to work with a proxy.
And in general, all asynchronous requests and streams do not support proxies.
The documentation suggests using the export of parameters as an env variable to solve this problem, like:
I propose to add a proxy as a request parameter to the creation of an asynchronous client.
As the example. AsyncClient.create starts with using ping to binance server. This ping doesn't get any kwargs to itself.
Adding more flexibility to the asynchronous part of working with proxies can greatly help with development. Especially in those countries where the binance is blocked by the ISP, and the api keys are tied to a given api address.
The text was updated successfully, but these errors were encountered:
Hi all!
It is not possible to adapt the work of your asynchronous part of the library to work with a proxy.
And in general, all asynchronous requests and streams do not support proxies.
The documentation suggests using the export of parameters as an env variable to solve this problem, like:
But this method didn't work for me.
I propose to add a proxy as a request parameter to the creation of an asynchronous client.
As the example. AsyncClient.create starts with using ping to binance server. This ping doesn't get any kwargs to itself.
Adding more flexibility to the asynchronous part of working with proxies can greatly help with development. Especially in those countries where the binance is blocked by the ISP, and the api keys are tied to a given api address.
The text was updated successfully, but these errors were encountered: