When uploading a Word document as an attachment for an alert, case, risk assessment, or entity, Microsoft Internet Explorer sometimes fails to correctly identify the file type. A content-type header for the attachment is sent indicating it to be a binary file (application or octet-stream).

When the document is subsequently viewed, the UI sends the file to the browser using the content-type header that was originally provided in the upload. If this value is application or octet-stream, the browser does not offer to open the file, requiring you to save the file locally before you can view it.

To correct this action, an additional property has been added to sasaml.config for SAS Anti-Money Laundering 4.2. This allows the original content type to be overridden by a value that is derived from the application server or from Java. Both of these sources can be customized to define mappings from the extension on the filename to a content or mime-type value. Where neither the application server nor Java provide a mapping, the SAS Anti-Money Laundering UI falls back to sending the original content type. For SAS Anti-Money Laundering 5.1 and 5.2, this property is accessed in the SAS^® Management Console.

Web applications can provide a file extension to mime-type mappings in their WEB-INF\WEB.XML file as <mime-mapping> elements. The hosting application server might provide a propriety extension to this mechanism, including a default set of mappings. Java provides a file extension to mime-type mapping using the {JRE}\lib\content-type.properties file.

Operating System and Release Information

A fix for this issue for SAS Anti-Money Laundering 4.2 is available at:

A fix for this issue for SAS Anti-Money Laundering 5.1_M1 is available at:

A fix for this issue for SAS Anti-Money Laundering 5.1 is available at: