We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If you want to use "http://localhost:8888" to proxy your application "https://baidu.com", but in "requess.go" that code use proxy environment.
I don't known why the proxies shoud be a map, and I want to known send a request why should need more proxies url.
Because I could code this
I think this code will let grequests wrong, Because it doesn't known how to select proxy, there has two proxy server.
I want to pull requet, but my English is so bad. I hope this can help other people who is using grequests.
And, I think ssl agent should be support in proxies .
ro := &grequests.RequestOptions{ Proxies: []interface{"user-agent": "xx", pUrl: "http://xx:8080"} }
Because if don't set ssl user agent, the remote serve may be check ssl user-aget
The text was updated successfully, but these errors were encountered:
I love you baby. 希望你听到这句话不要太尴尬。你能够解决那些不好特性吗?不要模仿python 的 requests,让我们一起改变这个世界。
Sorry, something went wrong.
No branches or pull requests
If you want to use "http://localhost:8888" to proxy your application "https://baidu.com", but in "requess.go" that code use proxy environment.
I don't known why the proxies shoud be a map, and I want to known send a request why should need more proxies url.
Because I could code this
I think this code will let grequests wrong, Because it doesn't known how to select proxy, there has two proxy server.
I want to pull requet, but my English is so bad. I hope this can help other people who is using grequests.
And, I think ssl agent should be support in proxies .
Because if don't set ssl user agent, the remote serve may be check ssl user-aget
The text was updated successfully, but these errors were encountered: