Tickets :: Comment on [#11017] precompress files in /static

* Your Email Address
* Spam protection	Enter the letters below: . ..___.. ..__ . . \|\/\| \| \|\ \|[__)\ / \| \| \| \| \\|[__) \/
Comment	> With pre-compression I mean to extend Horde to create for each > static/f.js a corresponding static/f.js.gz and for each static/k.css > a corresponding static/k.css.gz file at the same time the original > file (without .gz) is created. > > When a browser requests static/m.js and does Accept-Encoding: gzip, > the webserver checks if static/m.js.gz exists, and sends > static/m.js.gz to the browser,(instead static/m.js) stating the > response is gzip-encoded. > > I know the payload for any html page is not known until the page is > created, however this is not true exactly true for javascript/css > files, which are created once but delivered several times. > > I think this functionality belongs to Horde and it is not up to each > single administrator to find ways to compress the .js/.css files from > static/ .
Attachment
Watch this ticket