Changes between Initial Version and Version 1 of Ticket #3244


Ignore:
Timestamp:
04/01/2019 11:33:21 AM (6 years ago)
Author:
Calum
Comment:

Based on your use-case I agree that this would be good to fix.

Using the Twisted resource wrapper is a better way to do this and I have created a PR: ​https://github.com/deluge-torrent/deluge/pull/233

We should also only compress text and not images and that can be included in the changes.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3244

    • Property Component Unknown → Web UI
    • Property Milestone needs verified → 2.x

  • Ticket #3244 – Description

    initial v1  
    11At 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.
     2
     3Personally, 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.
    24
    35To reproduce, run: