Bug #2068
closedmod_expire adding Cache-Control header
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
Updated by glen about 15 years ago
- File expire2.patch expire2.patch added
- Target version set to 1.4.24
proposed patch. tested works:
Cache-Control: public, max-age=3024000
Updated by glen about 15 years ago
- Status changed from New to Fixed
- % Done changed from 90 to 100
Applied in changeset r2621.
Updated by pioklo almost 15 years ago
Hello !
Its possible to append this patch into 1.5.x ?
regards,
Piotr
Updated by glen almost 15 years ago
- File expire-1.5.patch expire-1.5.patch added
- Missing in 1.5.x set to Yes
patch against r2704, please test and report back!
Updated by pioklo almost 15 years ago
if (NULL != (ds = (data_string *)array_get_element(con->response.headers, key))) {
should be
if (NULL != (ds = (data_string *)array_get_element(con->response.headers, key,keylen ))) {
I have have tested this patch and my few servers working fine
Regards,
Piotr Kloc
Updated by glen almost 15 years ago
- File expire-1.5b.patch expire-1.5b.patch added
Updated by demimurych over 13 years ago
File expire-1.5b.patch have error
in line
if (NULL != (ds = (data_string *)array_get_element(con->response.headers, key, leylen))) {
should be
if (NULL != (ds = (data_string *)array_get_element(con->response.headers, key, keylen))) {
leylen => keylen
Also available in: Atom