tracker issue : CF-3321442

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

CFLayout does not load properly with SSL (https), works fine with http

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Mike Collins / Mike Collins (Mike Collins)

Created: 08/30/2012

Components: AJAX

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final /

Priority/Frequency: Critical / All users will encounter

Locale/System: English / Windows 7 64-bit

Vote Count: 0

Problem Description: When using cflayout with ssl the domcontentloaded event seems to fire too early and you end up with an object not defined error which then stops the layout objects from being visible.

Steps to Reproduce:
Get sample code from doc.
http://help.adobe.com/en_US/ColdFusion/10.0/CFMLRef/WSc3ff6d0ea77859461172e0811cbec22c24-7a22.html
Run inside http then run with https.
I tested IE and Chrome and both have issues with SSL

Actual Result:  Layout objects are not created
In the _cflayout_init_12345678 event which is triggered by the Domcontentloaded event you will see that the DOM is not actual ready.
All resource files appear to load fine.  All are served with https.

Expected Result:  Expect events to fire like http

Any Workarounds: none that I know.  Need to find a better trigger for the Domcontentloaded event.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3321442

External Customer Info:
External Company:  
External Customer Name: mcollins323
External Customer Email:  
External Test Config: My Hardware and Environment details: NA

Attachments:

Comments:

We are not able to reproduce this with a self signed certificate on both IE and Chrome. Is there anything specific that you are doing ? What was the workaround that you used to fix it ?
Comment by Himavanth R.
18252 | September 07, 2012 03:27:20 AM GMT
Closing the bug as "Not a Bug" since we were not able to reproduce the issue at our end, and did not receive any additional information from the customer. If this bug still exists on your environment, please report back, and we will be reopening this bug.
Comment by Immanuel N.
18253 | December 03, 2014 01:25:13 AM GMT