|Summary:||hard to force Content-Type header for non static files|
|Product:||Apache httpd-2||Reporter:||Eric Covener <covener>|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description Eric Covener 2010-08-23 08:37:29 UTC
Generally, directives that manipulate types run early in request procesing and have their work undone by generators that call ap_set_content_type(). Meanwhile, mod_headers even as a filter runs before the HTTP header output filter pulls r->content_type and adds it as a header. It would be nice if e.g. ForceType could be consulted somewhere prior to the header going from the internal representation into the Content-Type header. (reported on IRC as ForceType, RewriteRule .. [T=] and mod_headers can't change Content-Type of a proxied response. Really applies to almost any non-core handler)
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:42 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.