Custom Query (2447 matches)

ui/web/json_api.py:

    def _on_rpc_request_failed(self, reason, response, request):
        """
        Handles any failures that occurred while making an rpc call.
        """
        request.setResponseCode(http.INTERNAL_SERVER_ERROR)

Above code will never send back a JSON-RPC response to the browser. Causing the browser to time-out. This can easily be reproduced by raising an DelugeError exception in one of the Deluge daemon @export RPC methods.

As a result exceptions can't be used to inform browser on RPC failures. Note that there is also no other mechanism in Deluge to create JSON-RPC error responses. Making it hard to handle errors generically in the browser.

It would be sweet if a single proxy selection could be used to set the proxy preference for Peer, Web Seed, Tracker, and DHT connections in one fell swoop, rather than having to set each of these individually.

In my experience, I rarely want or need to set different proxy settings for these different protocol request types, but when I do want to use a proxy, I want to use it for all connections. For bonus points, it would be nice if there were another option (the default?) to "Use the system proxy settings" that would simply use whatever the OS's current configured proxy is, since that's usually what I'm setting proxy settings to, anyway. :)

Thanks for such a great piece of software.

Could you turn off passkey exposure by default? This option turned off will let rutracker.org's administration unban Deluge and finally stop this useless fight.