tracker issue : CF-3734962

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

cfwebsocket not working (JS not inserted)

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Sean Ford / Sean Ford (seanpford)

Created: 04/02/2014

Components: Web Socket

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: PublicBeta /

Priority/Frequency: Critical / All users will encounter

Locale/System: ALL / Win 2012 Server x64

Vote Count: 0

Duplicate ID:	CF-3853569

Problem Description: Using cfwebsocket in CF11 does not work. The Javascript is never inserted into the page.

Steps to Reproduce: place cfwebsocket on page

Actual Result: nothing

Expected Result: websocket JS inserted to allow socket communication

Any Workarounds:

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

Watson Bug ID:	3734962

External Customer Info:
External Company:  
External Customer Name: seanpford
External Customer Email:  
External Test Config: My Hardware and Environment details: Windows 2012 R2 with IIS8



You might need to give Adobe more to go on, because it works OK on my install. So it's not intrinsically broken... must be something to do with your rig. Also might help if you were more explicit with your repro case (ie: post some *actual code* that works on CF10, but doesn't on CF11) -- Adam
Comment by External U.
12898 | April 02, 2014 05:53:09 AM GMT
I've figured out why this was not working. I have a Custom Tag that I use to insert reusable code at the top of each page. I starts outputting at the doctype, and finishes with the closing HEAD tag. I use variables to change the title, security roles allowed, etc. and can include page-specific tags by including them between the opening and closing custom tags. Inside of this tag, there was a <cfcontent reset="yes"> at the very top of the <cfif thistag.ExecutionMode IS "start"> statement to make sure that the doctype was the first thing outputted. In CF 8, 9, and 10, this worked as designed. In CF11, this tag seemingly wiped out the Javascript inserted by the cfwebsocket tag. Removing it fixed the issue. However, it is a breaking change that MAY affect others, so I'm filing the bug anyways so that it can either be changed or at least documented.
Comment by External U.
12899 | April 02, 2014 10:59:52 AM GMT
Hi Sean, Can you please attach a repro case so that we can investigate it further?
Comment by Nimit S.
12900 | April 03, 2014 12:04:24 AM GMT
How would I do this?
Comment by External U.
12901 | April 29, 2014 08:59:20 PM GMT
You can send it to
Comment by Nimit S.
12902 | April 30, 2014 10:33:20 PM GMT
Hi Sean, Are you still facing this issue? can you please attach a repro case using which I can observe this issue? Because I am not facing this issue and I am able to use cfwebsocket tag perfectly fine. Regards, Nimit
Comment by Nimit S.
12903 | December 01, 2014 03:55:34 AM GMT