FranklinDM 091a2aab80 No issue - Make content-type on JAR channels behave the same as HTTP channels ... This ensures that the content type is also determined when opening JAR channels both synchronously and asynchronously. Current m-c modifies only the async portion, while the mentioned commit below modifies only the sync portion. This commit does it for both. Partially based on 425677ada7380f7c592dd01ddfbc9631ab2038a0 and bug 1757604.		2023-03-14 22:12:05 +08:00
..
test
zipwriter	Issue #1656 - Part 6: Clean up the build files	2020-09-25 22:04:23 +08:00
appnote.txt
moz.build	Issue #1656 - Part 6: Clean up the build files	2020-09-25 22:04:23 +08:00
nsIJARChannel.idl
nsIJARFactory.h
nsIJARProtocolHandler.idl
nsIJARURI.idl
nsIZipReader.idl
nsJAR.cpp	Issue #1656 - Part 1: Nuke most vim config lines in the tree.	2020-09-25 22:04:12 +08:00
nsJAR.h
nsJARChannel.cpp	No issue - Make content-type on JAR channels behave the same as HTTP channels	2023-03-14 22:12:05 +08:00
nsJARChannel.h	No issue - Make content-type on JAR channels behave the same as HTTP channels	2023-03-14 22:12:05 +08:00
nsJARFactory.cpp
nsJARInputStream.cpp	Issue #1683 - Update libjar module.	2020-11-16 21:10:23 +08:00
nsJARInputStream.h	Issue #1683 - Update libjar module.	2020-11-16 21:10:23 +08:00
nsJARProtocolHandler.cpp
nsJARProtocolHandler.h
nsJARURI.cpp
nsJARURI.h
nsZipArchive.cpp	[libjar] Add some extra sanity checks to our Zip reader.	2022-12-16 11:24:45 +08:00
nsZipArchive.h	Issue #1683 - Update libjar module.	2020-11-16 21:10:23 +08:00
zipstruct.h	Issue #1683 - Update libjar module.	2020-11-16 21:10:23 +08:00