mod_headers/5769: mod_headers won't append to Cache-Control header created by mod_expires

[Jason Priebe <pr...@wral-tv.com>]

>Number:         5769
>Category:       mod_headers
>Synopsis:       mod_headers won't append to Cache-Control header created by mod_expires
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Feb 16 13:50:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     priebe@wral-tv.com
>Release:        1.3.9
>Organization:
apache
>Environment:
RH Linux 5.2, kernel 2.0.36, i686
>Description:
At the server level, we set this directive for mod_headers:

Header append Cache-Control "public, must-revalidate"

then at the Directory level, we set these directives for mod_expires:

ExpiresActive On
ExpiresDefault "modification plus 4 hours"

Our goal is to get a Cache-Control header like this:

Cache-Control: max-age=13871, public, must-revalidate

However, the only Cache-Control header we get from the server is this:

Cache-Control: max-age=13871

I have tried two variations on this.  I have changed "append" to
"set".  Still no "public, must-revalidate" in the Cache-Control
header.  I then tried removing the mod_expires directives.  Then
I got:

Cache-Control: public, must-revalidate


>How-To-Repeat:
I found another user mentioning this problem on DejaNews.  He was
using the NT version, so I guess that it's fairly widespread.

Here are the modules I've got compiled in (the only non-standard
ones are usertrack, rewrite, headers, and expires):

Compiled-in modules:
  http_core.c
  mod_env.c
  mod_log_config.c
  mod_mime.c
  mod_negotiation.c
  mod_status.c
  mod_include.c
  mod_autoindex.c
  mod_dir.c
  mod_cgi.c
  mod_asis.c
  mod_imap.c
  mod_actions.c
  mod_userdir.c
  mod_alias.c
  mod_rewrite.c
  mod_access.c
  mod_auth.c
  mod_expires.c
  mod_headers.c
  mod_usertrack.c
  mod_setenvif.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]