https://bz.apache.org/bugzilla/show_bug.cgi?id=64237
Bug ID: 64237 Summary: Mime-mapping for *.Z files is missing in default configuration of Tomcat 7.0.103 Product: Tomcat 7 Version: trunk Hardware: PC Status: NEW Severity: regression Priority: P2 Component: Catalina Assignee: dev@tomcat.apache.org Reporter: knst.koli...@gmail.com Target Milestone: --- The following commit removed the <mime-mapping> for "Z" files from the default conf/web.xml, under assumption that Tomcat 7 processes mime mappings in case-insensitive manner: https://github.com/apache/tomcat/commit/fa587753d13125573118cfd6bad46dce6088b857 Smoke-testing Tomcat 7.0.103, it does not. Using a sample file, placed into the ROOT webapp (named "foo.Z", then "foo.z"): wget.exe --save-headers http://localhost:8080/foo.Z [[[ HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Accept-Ranges: bytes ETag: W/"6-1584539021767" Last-Modified: Wed, 18 Mar 2020 13:43:41 GMT Content-Length: 6 Date: Wed, 18 Mar 2020 13:46:45 GMT Test ]]] wget.exe --save-headers http://localhost:8080/foo.z [[[ HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Accept-Ranges: bytes ETag: W/"6-1584539021767" Last-Modified: Wed, 18 Mar 2020 13:43:41 GMT Content-Type: application/x-compress Content-Length: 6 Date: Wed, 18 Mar 2020 13:47:44 GMT Test ]]] The Content-Type header is missing from the first response. Testing Tomcat 8.5.53, it returns Content-Type header as expected. One of the options to fix this is to backport case-insensitive mime-type mapping to Tomcat 7. The feature was implemented in Tomcat 8.0.0 with r1356151: https://bz.apache.org/bugzilla/show_bug.cgi?id=45995 https://github.com/apache/tomcat/commit/2a18548f51cf89694077f4f72605190a8e7a427e -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org