search

defiantredpill / transmisson-remote-gui

Automatically exported from code.google.com/p/transmisson-remote-gui
0 stars 0 forks source link

Digest authentication is not supported when connection via proxy (only Basic auth is supported) #221

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install latest transmission from source
2. Config Lighttpd proxy front end according to Wiki
(http://trac.transmissionbt.com/wiki/WebProxy)
3. Connect to transmission server via Transmission Remote

* The web interface works as expected.
* Disabling auth in Lighttpd fixes the issue.
* Tried changing realm name to just "Transmission" vs "Transmission Web
Interface" like specified in the wiki. No go.

Original issue reported on code.google.com by romanfil...@gtempaccount.com on 14 May 2010 at 8:15

Attachments:

GoogleCodeExporter commented 9 years ago 
Hmm, did you specify a user name and a password in the transgui connection 
settings?

Original comment by j...@cp-lab.com on 15 May 2010 at 9:16

GoogleCodeExporter commented 9 years ago 
Yes, I did.

Original comment by romanfil...@gtempaccount.com on 15 May 2010 at 3:00

GoogleCodeExporter commented 9 years ago 
No idea how to fix that, because I do not have a proxy...

Original comment by j...@cp-lab.com on 3 Aug 2010 at 11:26

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 3 Aug 2010 at 11:28

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 26 Aug 2010 at 2:24

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 26 Aug 2010 at 2:28

GoogleCodeExporter commented 9 years ago 
I spent most of the night trying to figure out how to use SSL with Transgui.
I tried Lighttpd and faced the same issue. I then tried Apache2... once again 
same issue.
Then I tried to switch to Basic AuthType and it finally worked !

It seems that transgui does not support the Digest AuthType

Original comment by peartoop...@gmail.com on 12 Nov 2010 at 1:59

GoogleCodeExporter commented 9 years ago 
Indeed, transgui uses the basic http authentication, which is expected by the 
transmission daemon. Other authentication methods are not supported.

Original comment by j...@cp-lab.com on 12 Nov 2010 at 5:16

GoogleCodeExporter commented 9 years ago 
In fact I'm not using any password protection on the Transmission Daemon.
I just limited its access to 127.0.0.1 and then set up an SSL WebProxy 
redirection on Apache2.

I'm just a n00b in all of these technologies, but I thought that the 
authentification was taken care of by Apache2.
Am I wrong ?

Original comment by peartoop...@gmail.com on 13 Nov 2010 at 7:29

GoogleCodeExporter commented 9 years ago 
Probably you should enable authentication in the transmission daemon and 
disable it in the proxy.

Original comment by j...@cp-lab.com on 13 Nov 2010 at 7:52

GoogleCodeExporter commented 9 years ago 
Thanks for your feedback.
I discovered a few hours ago that transmisson-remote-gui can go through both 
Apache SSL and Transmission authentication, as long as l/p on both are 
identical !
I never expected it to work but it does work great.
I love transmisson-remote-gui more than ever. This software is amazing.

Original comment by peartoop...@gmail.com on 14 Nov 2010 at 3:28

GoogleCodeExporter commented 9 years ago 
Some how I ended up here wile looking for Transmission Remote. The SSL 
functionality is a non-starter for this product. 

Transmission Remote dotnet @: 
http://code.google.com/p/transmission-remote-dotnet/ works fine with Digest 
AuthType.

Original comment by nomadr...@gmail.com on 12 Dec 2010 at 1:06

GoogleCodeExporter commented 9 years ago 
Synapse libarary does not support Digest authentication. I have no interest to 
implement it...

Original comment by j...@cp-lab.com on 20 Feb 2011 at 2:26

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 1 Mar 2011 at 9:53