Custom Query (2447 matches)
Results (64 - 66 of 2447)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2455 | Invalid | "Not connected" after browser refresh | ||
Description |
After doing a browser refresh, the deluge web-ui reports in the lower left corner in the status bar: "Not connected". Now when opening the connection manager, it shows the deluge daemon perfectly as "connected". However, I can only click "Disconnect" to really disconnect from the daemon and the click "Connect" to connect to it again. Expected behavior: I would expect that the web-ui stays connected after a browser refresh. |
|||
#2724 | Fixed | JSON-RPC not forwarding exceptions/errors causing browser to time-out on calls | ||
Description |
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. |
|||
#284 | WontFix | Deluge WebUI Plugin contains an invalid security certificate | ||
Description |
when attempting to connect to the deluge webUI using http secure, firefox 3.0 report an invalid security certificate, and refuse to connect (unless an exception is setup, in the case of firefox) thanks! |