Add ability to set maximum size of a resource for mod_pagespeed to optimize

[GoogleCodeExporter]

From a user report:

if there is a request for a huge file then mod pagespeed goes for a spin and 
the RAM usage bloats up. Is there a way to tune this, or ask modpagespeed to 
not process if the response size is bigger than a certain limit. Currently we 
are handling by having a cron that kill any httpd process that exceeds a 
certain RAM usage size. 

Original issue reported on code.google.com by jmara...@google.com on 19 Sep 2012 at 12:35

[GoogleCodeExporter]

Original comment by jmara...@google.com on 19 Sep 2012 at 12:35

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by jmara...@google.com on 30 Oct 2012 at 9:58

[GoogleCodeExporter]

Original comment by matterb...@google.com on 10 Dec 2012 at 8:13

• Added labels: Milestone-v24, release-note

[GoogleCodeExporter]

Add "ModPagespeedMaxCacheableContentLength" to the configuration options.

Original comment by hui...@google.com on 10 Dec 2012 at 8:17

• Changed state: Fixed