Project

General

Profile

Bug #1172

mod_compress will suppress mod_expire

Added by brainsik over 12 years ago. Updated almost 11 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
mod_compress
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

If mod_compress is loaded before mod_expire then pages which are sent compressed will not have expires headers sent regardless of the expires configuration. By loading mod_expire first, pages can be sent both compressed and with expires headers.

I edited the documentation wiki to reflect this situation.

History

#1

Updated by brainsik over 12 years ago

Sorry, I forgot to change the version to 1.4.13 (though I suspect it's present in 1.4.15 given the changelog for 1.4.13 -> 1.4.15).

#2

Updated by brainsik almost 12 years ago

Should have added this link long ago -- this bug may be related to this one: http://trac.lighttpd.net/trac/ticket/1171

#3

Updated by stbuehler over 11 years ago

Some comments on mod_compress:
- Only compresses static files
- If you don't use compress.cache-dir, it behaves like other content-producing modules, i.e. mod_fastcgi. Other modules after it get ignored (handler return code HANDLER_FINISHED).

I attach a patch to generate etag/last-modified in this case too
- If you use compres.cache-dir, it redirects the physical path to the compressed file, so modules after it can work with that.

So this is a problem by design and won't get fixed - mod_compress could only do it itself.

#4

Updated by stbuehler about 11 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid
#5

Updated by stbuehler almost 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom