Custom Query (2447 matches)
Results (112 - 114 of 2447)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3244 | Fixed | Use gzip content encoding only if supported by client | ||
| Description |
At the moment deluge responds to requests for certain resource with gzip content encoding regardless of the requests 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 127.0.0.1:8112/js/ext-extensions.js -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: https://github.com/deluge-torrent/deluge/pull/232 |
|||
| #3233 | Duplicate | Deluge 1.3.15 breaks with libtorrent-1.2 | ||
| Description |
libtorrent-rasterbar >= 1.2 removes several functions required by deluge. Upstream bug is: https://github.com/arvidn/libtorrent/issues/1510 Gentoo bug is: |
|||
| #3232 | WontFix | Migrate to libtorrent-1.2 | ||
| Description |
libtorrent-rasterbar >= 1.2 removes several functions required by deluge. Upstream bug is: https://github.com/arvidn/libtorrent/issues/1510 Gentoo bug is: |
|||
