Data Control rule doesn't work on .JAR Files when it is configured to match by File Attribute where Content Type is "Source Code".
The following Data Control rule was set up to Block the downloading of files with a Content Type identified as "source_code."
Next, we proceed to download two .jar files:
The download of
java-1.0.jar was completed successful.
However, the download of
sample.jar was blocked.
Why is the same rule treating these two .jar files differently?
The reason is because a .jar file can either be a Zip archive or a specialized Java archive (JAR) file. When identified as a Zip archive, the aforementioned rule, configured to match by File Attribute where Content Type is "Source Code", would therefore result in no match. This explains on why the first file,
java-1.0.jar, was not blocked during the download process.
We can use the
Filecommand in Linux to find out the content type of the .jar file.
$ file java-1.0.jar
$ file sample.jar