tracker issue : CF-4204094

select a category, or use search below
(searches all categories and all time range)
Title:

CFHTMLTOPDF unexpected behavior in Sandboxed environments using the latest hotfix. CF11 ++

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): dakota c. / ()

Created: 03/12/2019

Components: Document Management, PDF Generation (CFHTML2PDF)

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: ColdFusion 11 Update 18 /

Priority/Frequency: Normal / All users will encounter

Locale/System: ALL / Win 2012 Server x64

Vote Count: 1

Problem Description: Beginning in the latest ColdFusion hotfixes any websites utilizing a sandbox security environment present the following error when using <cfhtmltopdf>:

"Could not initialize class coldfusion.document.webkit.PDFgRequestUtil"

This issue was also reported in the following Adobe forum post with a workaround provided: https://forums.adobe.com/thread/2601739

Steps to Reproduce: Run the following code snippet on a website using Sandbox Security: 

<cfhtmltopdf source="http://www.google.com/" />

In our testing, we've found that this issue is present in ColdFusion 11 and ColdFusion 2016.

Actual Result: "Could not initialize class coldfusion.document.webkit.PDFgRequestUtil" (500: Internal Server Error)

Expected Result: A PDF generated from the source attribute https://google.com. 

Any Workarounds: The workaround is to add the following Sandbox Paths to the site's sandbox security entry: 

C:\ColdFusion[Version]\cfusion\lib\configure_9_3.dtd, Read
C:\ColdFusion[Version]\cfusion\lib\jetty.xml, Read

Replace "[Version]" with the respective version of ColdFusion being used. 

Credit: https://forums.adobe.com/thread/2601739

We've experienced this behavior in multiple environments using sandbox security.

Attachments:

Comments:

This is a duplicate of the bug: CF-4204080, hence closing this.
Comment by Kailash B.
30490 | March 13, 2019 06:32:18 AM GMT
https://tracker.adobe.com/#/view/CF-4204080 I'm unable to view this bug tracker. Does it still exist?
Comment by dakota c.
30493 | March 13, 2019 02:52:25 PM GMT