Project

General

Profile

Actions

Bug #2068

closed

mod_expire adding Cache-Control header

Added by glen over 15 years ago. Updated about 14 years ago.

Status:
Fixed
Priority:
Normal
Category:
mod_expire
Target version:
ASK QUESTIONS IN Forums:

Description

seems if mod_env combined with mod_expires to have such headers breaks:

    expire.url = (
        "/" => "access plus 5 weeks",
    )

    setenv.add-response-header += (
        "Cache-Control" => "public" 
    )
Cache-Control: public
Cache-Control: max-age=3024000

while the expected result is:

Cache-Control: public, max-age=3024000


Files

expire2.patch (2.15 KB) expire2.patch patch. tested. works glen, 2009-09-18 12:40
expire-1.5.patch (2.19 KB) expire-1.5.patch patch for 1.5 glen, 2010-01-21 08:48
expire-1.5b.patch (2.19 KB) expire-1.5b.patch bugx glen, 2010-01-22 14:25

Added by glen over 15 years ago

Revision 2621 (diff)

- Combine Cache-Control header value in mod_expire to existing HTTP header if header already added by other modules (fixes #2068)

Added by glen over 15 years ago

Revision 6c75b7bf (diff)

- Combine Cache-Control header value in mod_expire to existing HTTP header if header already added by other modules (fixes #2068)

git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@2621 152afb58-edef-0310-8abb-c4023f1b3aa9

Added by glen about 14 years ago

Revision 2781 (diff)

- Combine Cache-Control header value in mod_expire to existing HTTP header if header already added by other modules (fixes #2068)

Actions

Also available in: Atom