I get "can't unzip" error with goagent

[Rambin]

I get a "can't unzip" error when I add a torrent from the URL such as http://bt.ktxp.com/torrents/2013/08/22/f02c8d1ce7e290fa863f614111c5eb1c62494672.torrent with goagent, but it works when I turned off proxy.

I captured the TCP stream and find that the HTTP headers is a little different.

=======without goagent========

GET /torrents/2013/08/22/f02c8d1ce7e290fa863f614111c5eb1c62494672.torrent HTTP/1.1

Host: bt.ktxp.com

User-Agent: BTWebClient/3300(29038)

Accept-Encoding: gzip

Connection: Close

HTTP/1.1 200 OK

Server: nginx/1.4.1

Date: Thu, 22 Aug 2013 01:58:25 GMT

Content-Type: application/octet-stream

Content-Length: 18967

Last-Modified: Thu, 22 Aug 2013 00:54:51 GMT

ETag: "5215615b-4a17"

Accept-Ranges: bytes

Age: 2916

X-Cache: HIT from cloud.rds.7

X-Cache: MISS from cloud.5

Via: 1.1 cloud.rds.7:87 (squid), 1.1 cloud.5:85 (squid)

Connection: close

========with goagent=======

GET http://bt.ktxp.com/torrents/2013/08/22/f02c8d1ce7e290fa863f614111c5eb1c62494672.torrent HTTP/1.1

Host: bt.ktxp.com

User-Agent: BTWebClient/3300(29038)

Accept-Encoding: gzip

Connection: Close

HTTP/1.1 200

Server: nginx/1.4.1

Date: Thu, 22 Aug 2013 02:23:46 GMT

Content-Type: application/octet-stream

Content-Length: 18967

Last-Modified: Thu, 22 Aug 2013 00:54:51 GMT

Etag: "5215615b-4a17"

Accept-Ranges: bytes

Connection: keep-alive

Age: 375

Via: HTTP/1.1 GWA (remote cache hit)

=========and another site with goagent=========

GET http://www.nyaa.se/?page=download&tid=465576 HTTP/1.1

Host: www.nyaa.se

User-Agent: BTWebClient/3300(29038)

Accept-Encoding: gzip

Referer: http://www.nyaa.se/?page=download&tid=465576

Connection: Close

HTTP/1.1 200 OK

Content-Length: 20113

Via: HTTP/1.1 GWA (remote cache hit)

Content-Disposition: inline; filename="Science ZERO - 2013-08-18 (NHK-E 1280x720 h264 AAC).mkv.torrent"

Content-Encoding: gzip

Age: 22

Vary: Accept-Encoding

Server: :3

Last-Modified: Thu, 22 Aug 2013 08:24:36 GMT

Connection: keep-alive

Date: Thu, 22 Aug 2013 08:27:24 GMT

Content-Type: application/x-bittorrent

It seems that the main different between with and without goagent is that the "Connection" property is "keey-alive" when using goagent, and "nyaa.eu" said that it's encoded in gzip but "ktxp.com" said nothing and using flat text.

Is UT treat no sign stream in keep-alive connection as a gzip stream?

Apologize for my poor English.

[ciaobaby]

but it works when I turned off proxy.

Therefore the problem is the proxy NOT uTorrent.

[Rambin]

but it works when I turned off proxy.

Therefore the problem is the proxy NOT uTorrent.

I said it works well with another site, and I forgot to say that any browser with the proxy works too.

So I get this error only when I use UT and the proxy.

I have submitted this issue on the project page of the proxy.

[ciaobaby]

Browsers use HTTP not BitTorrent.

[Rambin]

Browsers use HTTP not BitTorrent.

But the protocol UT used to get a torrent from RSS is HTTP.

I didn't check "Use proxy for P2P connections", so that only tracker communication and RSS uses proxy.

[DreadWingKnight]

Works without proxy but not with means the bug is in the proxy.

[ciaobaby]

But the protocol UT used to get a torrent from RSS is HTTP.

Yes just like YOU use HTTP to get magnets or download .torrent files, but ONCE the job is loaded into the client, ... HTTP is finished with and the torrent payload data is downloaded using the BitTorrent protocol.

[Rambin]

But the protocol UT used to get a torrent from RSS is HTTP.

Yes just like YOU use HTTP to get magnets or download .torrent files' date=' but [b']ONCE the job is loaded into the client, ... HTTP is finished with and the torrent payload data is downloaded using the BitTorrent protocol.

But what I faced is that the job can't be loaded into UT.

I get "can't unzip" before the job appears.

[DreadWingKnight]

Most likely because the proxy is doing something it shouldn't be.

AKA, NOFF

[Rambin]

Most likely because the proxy is doing something it shouldn't be.

AKA, NOFF

I think that the proxy is with some bug too.

But if a browser works well with the proxy in same action, UT is no reason to fail, in my opinion.

[DreadWingKnight]

It's a bug in the proxy, not in uTorrent.