Transmission

mariad_10 wrote:hey, did the app download and i think it is working great. Just to thank you keep up the good work.

payeco wrote:

Monitor.app wrote:

payeco wrote:
I know this connects to the RPC path but that method won't work. The path has to be in the hostname and the way you have it set now paths can not be added to the hostname. When my server sees traffic to mydomain.com/transmission it redirects that traffic to <myserverip>:9091. The way you should probably is add servers is not having separate fields for hostnames/IPs and ports. Ideally they should all all just be added in the same field. If someone is using a custom port it would just be added in the hostname field as <serverip>:xxxx. (i.e. 192.168.0.23:9595). That way you can also allow people using reverse proxies to add them. Typically with apps like this that is how it works.

http://mydomain.com is the same thing as http://mymydomain.com:80

And https://mydomain.com is the same thing as https://mydomain.com:443

All HTTP traffic is TCP, and all TCP traffic has a port, just because you don't specify the port, doesn't mean there's no port. The default port for HTTP is 80 and HTTPS is 443.

Try http://www.google.com:80 for example...

I understand all that. Are you familiar with nginx and/or apache reverse proxies? Because that is what I'm using and the way your app works does not work with reverse proxies.

killemov wrote:Please rectify "Much more options than the WebUI." to "Much more options than the default WebUI a.k.a. Clutch."
Does the app use the base64 way of uploading torrent files?

kIssGlaY wrote:Does this app have search function? If it has, where is it? I simply can't find it.