mod_proxy/10176: Content-Type header disappearing on pages served from the Cache

[Anton Huenermann <ah...@opentext.com>]

>Number:         10176
>Category:       mod_proxy
>Synopsis:       Content-Type header disappearing on pages served from the Cache
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Mar 14 03:30:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     ahuenerm@opentext.com
>Release:        1.3.23
>Organization:
apache
>Environment:
Linux 2.4.4-64GB-SMP #1 SMP Wed May 16 01:20:45 GMT 2001 i686 unknown
Suse 7.2
>Description:
We have an application serving content  that is a mixture of html, pdf's, PowerPoint files and misc other mime types. We are using Apache as a Reverse Proxy in our DMZ and use the caching option. When we have a cache miss, the correct headers are passed through to the client browser. When we have a cache miss, the wrong mime-type is returned in the header. We've looked at the content of the cache directory, there the correct headers are still in the cached file, therefore there appears to be an error in the reading of content from the cache.

This problem has only started appearing since we updated to 1.3.23.
>How-To-Repeat:

>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!     ]