[Tickets #11017] Re: precompress files in /static

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11017
------------------------------------------------------------------------------
  Ticket             | 11017
  Updated By         | dpa-bugs at aegee.org
  Summary            | precompress files in /static
  Queue              | Horde Base
  Version            | 4.0.13
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


dpa-bugs at aegee.org (2012-02-21 09:01) wrote:

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/ .