Authentication troubles with protected rpc and SSL

[muff1nman]

I have nginx with SSL in front of transmission with a protected rpc. The app will not connect, saying there is an issue with the credentials.

What I know so far:

1. The web ui works fine
2. transmission-remote works fine. i.e: transmission-remote https://someip:443/transmission/rpc --debug -n 'user:password' -l
3. tcp dump show some interesting behavior:

• shows a successful request with method = get-session with correct X-Transmission-Session-Id, but then a second request is made with method = torrent-get but without the X-Transmission-Session-Id header which is then responded to with a 401
• not sure yet if this is accurate - will do another test to ensure i've isolated the http traffic correctly.

[sijanec]

Is there a server side hack for this? I have the same problem and I don't want to use unencrypted connection.