Transmission

BTW, it seems that the problem is with Content-length header which supposely should never be present in GET request. This confused tracker. Can't say whether tracker authors are right, I have not read RFC for a long time, but is this field actualy used for something in Transmission?

I need the actual text of request sent and response received, not just decoded response message. I have to use Wireshark or tcpdump to get them now. It would be nice to see this output in console window when the tracker is reachable but misbehaves or responds with an error.

ok this seems to be tracker-related issue. However, Transmission does not seem to provide a simple way to see that was sent to server and received in response (nothing on console). Not good...

Started getting this message when connecting to one of our local trackers. Tried to work with 0.9x as is but now will have to wait until they become more stable. The worst part is that app does not give any details on the error so I do not know where to start looking for the problem.