tracker issue : CF-4158043

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

Publishing large objects cause problems with Chrome using WebSockets

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Kyle Thompson / Kyle Thompson (Kyle Thompson)

Created: 05/26/2016

Components: Web Socket

Versions: 2016

Failure Type:

Found In Build/Fixed In Build: CF2016_Update1 /

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Windows 10 64 bit

Vote Count: 0

Duplicate ID:	CF-4154216

Problem Description:

Publishing large objects cause the frame to be encoded incorrectly for Chrome. However, it works correctly in Firefox.

Steps to Reproduce:

1. Open index.cfm in the attached zip file.
2. Open the console / developer tools for this tab.
3. Open spreadsPublish.cfm in another tab and observe the output of the console window for index.cfm.

Actual Result:

WebSocket connection to 'ws://127.0.0.1:8577/cfusion/cfusion' failed: Invalid frame header

Expected Result:

Console dump of the JSON transmitted over the WebSocket connection.

Any Workarounds:

None as far as I can find.

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

Watson Bug ID:	4158043

External Customer Info:
External Company:  
External Customer Name: Kyle Thompson
External Customer Email:  
External Test Config: My Hardware and Environment details:



Windows 10 64bit

Chrome 52.0.2743.6 dev-m (64-bit)

Can reproduce on ColdFusion 11 express and ColdFusion 2016 express.

Attachments:

  1. May 26, 2016 00:00:00: 1_websocket_test.zip

Comments:

Looks like I made a mistake, this isn't ColdFusion Builder 2016, but ColdFusion 2016 the application server.
Comment by External U.
2635 | May 26, 2016 09:12:03 AM GMT
Could I get what issue this is a duplicate of? I tried search the issue tracker for all three version that are currently supported and couldn't find the issue.
Comment by External U.
2636 | May 31, 2016 07:34:50 AM GMT
Nevermind, I found the duplicate id at the top of the ticket system... Not exactly the most user friend place to look for the duplicate at.
Comment by External U.
2637 | May 31, 2016 07:35:40 AM GMT