INC-129533 · Issue 576661
Proper MIME type kept for attachments
Resolved in Pega Version 8.5.1
When Email Listeners processed an email with an attachment and stored that attachment to an instance of DATA-WORKATTACH-FILE, it did not keep the full MIME type in the property pyAttachMimeType, but kept just the subtype (so "application/PDF" became "PDF" and "image/jpeg" became "jpeg"). As a consequence, the MIME type could not be reconstructed correctly when the file was attached to an outbound email. While most email clients were able to reconstruct (guess) the type of the file from the filename (or, more precisely, from the extension), this did not work when the email was processed by an automated system reliant on the correctly set Content-Type header. This has been corrected by reading the mime type from data-workattach-file page and setting the content type header while constructing the multipart with this value.
SR-D26913 · Issue 500208
Decision Table support added to customize MIME types
Resolved in Pega Version 8.4
ExtensionMimeDetector uses the Pega internal libraries property file "mime-types.properties" to return the MIME type. In order to facilitate customization such as a third party filenet system for processing that utilizes different MIME types, an override mechanism has been provided per file extension via a Decision Table for overriding the Pega defaults.
SR-D67232 · Issue 530008
Email listener updated to handle encoded MIME attachment
Resolved in Pega Version 8.2.6
When processing an email with an attachment that was itself an encoded MIME part, the email listener generated a NullPointerException around an extraction error. Analysis showed that a content-type misled the system into thinking an attachment was another message part. To resolve this, EmailMessageParser.java has been modified to avoid attempting to process an attachment as a MessagePart if it cannot get the content of the part as a Message.
SR-D67232 · Issue 530007
Email listener updated to handle encoded MIME attachment
Resolved in Pega Version 8.3.2
When processing an email with an attachment that was itself an encoded MIME part, the email listener generated a NullPointerException around an extraction error. Analysis showed that a content-type misled the system into thinking an attachment was another message part. To resolve this, EmailMessageParser.java has been modified to avoid attempting to process an attachment as a MessagePart if it cannot get the content of the part as a Message.
SR-D67232 · Issue 530009
Email listener updated to handle encoded MIME attachment
Resolved in Pega Version 8.5
When processing an email with an attachment that was itself an encoded MIME part, the email listener generated a NullPointerException around an extraction error. Analysis showed that a content-type misled the system into thinking an attachment was another message part. To resolve this, EmailMessageParser.java has been modified to avoid attempting to process an attachment as a MessagePart if it cannot get the content of the part as a Message.
SR-B64984 · Issue 314348
Web mashup mime header set in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When a response included the "X-Content-Type-Options: nosniff" header, the Microsoft Internet Explorer browser would not accept scripts and styles in case of mime-type mismatch. This was traced to the pzIncludeMashupScripts request not setting the mime type to text/JavaScript, and has been fixed.
SR-D37872 · Issue 507342
prproductmigration build.gradle updated for new mime4j asset name
Resolved in Pega Version 8.4
While running the getMigrationLog for ProductMigration script provided in the Pega 8.2.2 media files, errors appeared referencing "NoClassDefFoundErrors when running getLogs". This was caused by the referenced class not being found on the classpath: the version of the included jar did not include the class needed due to Praxiom's default version being updated to use a new version of mime4j that required an asset name change. To resolve this, the mime4j asset name in prproductmigration build.gradle has been updated to pick up the correct version of the dependency for Praxiom.
SR-D37872 · Issue 507341
prproductmigration build.gradle updated for new mime4j asset name
Resolved in Pega Version 8.2.4
While running the getMigrationLog for ProductMigration script provided in the Pega 8.2.2 media files, errors appeared referencing "NoClassDefFoundErrors when running getLogs". This was caused by the referenced class not being found on the classpath: the version of the included jar did not include the class needed due to Praxiom's default version being updated to use a new version of mime4j that required an asset name change. To resolve this, the mime4j asset name in prproductmigration build.gradle has been updated to pick up the correct version of the dependency for Praxiom.
SR-D37872 · Issue 507340
prproductmigration build.gradle updated for new mime4j asset name
Resolved in Pega Version 8.3.1
While running the getMigrationLog for ProductMigration script provided in the Pega 8.2.2 media files, errors appeared referencing "NoClassDefFoundErrors when running getLogs". This was caused by the referenced class not being found on the classpath: the version of the included jar did not include the class needed due to Praxiom's default version being updated to use a new version of mime4j that required an asset name change. To resolve this, the mime4j asset name in prproductmigration build.gradle has been updated to pick up the correct version of the dependency for Praxiom.
SR-D33096 · Issue 502742
pzGetURLHashes returns proper content-type
Resolved in Pega Version 8.4
When using an environment set with X-Content-Type-Options:nosniff, the response from pzGetURLHashes was returned with text/html response type and the mashup would not load due to browser exception "MIME Type ('text/html')is not excutable, and strict MIME type checking is enabled." In order to support CORB mitigation in the browser, the javascript content type will be set in the response header for pzGetURLHashes call.