Custom Query (2449 matches)


Show under each result:

Results (166 - 168 of 2449)

Ticket Resolution Summary Owner Reporter
#1363 WontFix Detect previously used settings in installer when upgrading tobbez

It would be nice if previously used settings (magnet link and torrent file association, GTK installation) were detected in the installer when upgrading, and their checkboxes automatically (un)checked.

#2338 Fixed typo in web UI (back-end) error message damoxc tmetro

When adding a torrent from a URL that fails to download, the web UI back-end logs:

[ERROR ] 16:56:57 json_api:661 Error occured downloading torrent from

"occured" is spelled wrong.

(I'm guessing this is in deluge/ui/web/

#3244 Fixed Use gzip content encoding only if supported by client tkSimon

At the moment deluge responds to requests for certain resource with gzip content encoding regardless of the requests accept-encoding header. It should only use gzip encoding if supported by the client.

Personally, I wanted deluge to respond with uncompressed assets because i have an nginx reverse proxy in front of deluge that's doing brotli (and gzip compression,) and caching those. The issue being that nginx only compresses when the origin (deluge) sends them uncompressed. This is usually achieved by configuring nginx to not forward the accept-encoding header.

To reproduce, run: curl -o /dev/null -v

The response will have a "Content-Encoding: gzip" header, and it's payload will be gzipped even though the request doesn't contain an "Accpet-Encoding: gzip" header.

I created a PR to fix this:

Note: See TracQuery for help on using queries.