On Sat, 5 Sep 2020, Hongyi Zhao wrote:
Is there really *anything* that implies that this is curl's fault and not
just something in Tor or even in the target server that just don't like
incoming traffic from Tor?
Any hints for debug/confirm this problem?
In general I would say that if curl w
On Fri, Sep 4, 2020 at 6:32 PM Daniel Stenberg via curl-library
wrote:
>
> On Sat, 5 Sep 2020, Hongyi Zhao via curl-library wrote:
>
> > werner@X10DAi-01:~$ curl -vI -x socks5://127.0.0.1:9050
> > https://www.baidu.com
>
> ...
> > As you can see, the connection to google succeed while fail for co
On Sat, Sep 5, 2020 at 6:29 AM Daniel Stenberg wrote:
>
> On Sat, 5 Sep 2020, Hongyi Zhao via curl-library wrote:
>
> > werner@X10DAi-01:~$ curl -vI -x socks5://127.0.0.1:9050
> > https://www.baidu.com
>
> ...
>
> > As you can see, the connection to google succeed while fail for connection
> > to
On Sat, 5 Sep 2020, Hongyi Zhao via curl-library wrote:
werner@X10DAi-01:~$ curl -vI -x socks5://127.0.0.1:9050 https://www.baidu.com
...
As you can see, the connection to google succeed while fail for connection
to baidu. Any hints for this problem?
Is there really *anything* that implies
Hi,
On Ubuntu 20.04, I run Tor which listens on 127.0.0.1:9050. The curl
testings for using Tor's socks5 proxy are done as following:
werner@X10DAi-01:~$ curl -vI -x socks5://127.0.0.1:9050 https://www.google.com
* Trying 127.0.0.1:9050...
* TCP_NODELAY set
* SOCKS5 communication to www.google.
