On Fri, Jan 8, 2016 at 3:17 PM, William A Rowe Jr <[email protected]> wrote: > On Fri, Jan 8, 2016 at 3:27 AM, Yann Ylavic <[email protected]> wrote: >> >> >> On Fri, Jan 8, 2016 at 8:49 AM, Jan Kaluža <[email protected]> wrote: >> > >> > Content-Type: application/x-tar >> > Content-Encoding: x-gzip >> > >> > So, the mod_mime_magic is saying here that the body is tarball encoded >> > by >> > gzip. >> >> AIUI, mod_mime_magic does indeed try to uncompress the tar.gz and adds >> the above headers. > > > Well, not strictly true, mod_deflate uncompresses it ;-)
Hmm, not sure mod_deflate is in the place, at least it doesn't need to AFAICT from the code. But sure mod_deflate could be configured to uncompress once more :) > >> > Maybe we could stop setting Content-Encoding in mod_mime_magic and just >> > use >> > Content-Type? >> >> Since it's always been there, we probably should add a new >> mod_mime_magic directive to control the behaviour and avoid breaking >> cases. > > > Agreed it is configuration, but cant we simply tweak our recommended > conf/magic > file??? > > # standard unix compress > # Enable the alternate line below to present gzip content as a transfer > encoded > # stream of the underlying content; > #0 string \037\235 application/octet-stream > x-compress > 0 string \037\235 application/octet-stream > > # gzip (GNU zip, not to be confused with [Info-ZIP/PKWARE] zip archiver) > # Enable the alternate line below to present gzip content as a transfer > encoded > # stream of the underlying content; > #0 string \037\213 application/octet-stream > x-gzip > 0 string \037\213 application/octet-stream > > WDYT? I wasn't aware of conf/magic file, but it seems not used by zmagic() which hardcodes its types. I may be missing something though...
