No worries Russ. Yes, I'm able to access 'CFIDE.websocket.ChannelListener' directly using the cfc browser.
Also, it seems that the <cfwebsocket> tag isn't creating the javascript websocket object at all, because when i try calling the startup functions directly thru the console, i get the error that the websocket object is not defined. This was never an issue before upgrading to CF11. On Wed, Jan 7, 2015 at 1:10 PM, Russ Michaels <r...@michaels.me.uk> wrote: > > ok sorry thought you were saying you could not lock down CFIDE cozz you > used web sockets. > > are you able to access the CFC directly via the browser using the cfc > browser? > > On Wed, Jan 7, 2015 at 12:44 PM, Parul Bali <parul.sarasw...@gmail.com> > wrote: > > > > > Thanks Russ, we do follow these practices on Production, but right now am > > testing locally. So was just ruling that out as the issue that might be > > breaking my Websockets' application which suddenly stopped working after > > upgrading to CF11. So was wondering if anyone's faced such Websocket > issues > > after upgrading to CF11. Any pointers or troubleshooting tips would be > > appreciated. > > > > On Wed, Jan 7, 2015 at 11:02 AM, Russ Michaels <r...@michaels.me.uk> > > wrote: > > > > > > > > The master CFIDE must be locked down, otherwise you are opening > yourself > > up > > > to be hacked. > > > One of the standard best practices I have documented since CF6 is to > > make a > > > copy of the CFIDE with only the minimal required files and to use this > as > > > the vDir in your sites if required. This will then contain nothing > > > dangerous that can be abused. > > > It is also fully documented in many places, including the lock down > guide > > > how to lock down only the parts of the CFIDE that need locking down if > > you > > > choose to use the original copy on your sites. > > > Have you tried this ? > > > > > > > > > On Wed, Jan 7, 2015 at 9:38 AM, Parul Bali <parul.sarasw...@gmail.com> > > > wrote: > > > > > > > > > > > Bryon, > > > > > > > > My custom channel listener does extend > > 'CFIDE.websocket.ChannelListener', > > > > but if CFIDE's Channel Listener is inaccessible, I get the error that > > my > > > > custom ChannelListener is not a valid ChannelListener handler. So > > > locking > > > > down of CFIDE is ruled out. > > > > > > > > Thanks > > > > > > > > On Wed, Jan 7, 2015 at 8:45 AM, Parul Bali < > parul.sarasw...@gmail.com> > > > > wrote: > > > > > > > > > Hi Bryon, > > > > > > > > > > I use my own custom channel listener CFC. So that's probably not > the > > > > > issue. Thanks for your help. > > > > > > > > > > Hi Jack, > > > > > > > > > > The websockets are enabled in CFAdmin. Thanks. > > > > > > > > > > It was working right before the upgrade to CF11, so wondering if > > > there's > > > > > anything to be kept in mind while upgrading - that I might have > > missed. > > > > > > > > > > On Wed, Jan 7, 2015 at 4:09 AM, Jack Traynor < > traynor.j...@gmail.com > > > > > > > > wrote: > > > > > > > > > >> > > > > >> There is an option in CFAdmin that enables websockets, make sure > > that > > > is > > > > >> still enabled after your upgrade. > > > > >> > > > > >> On Wed, Jan 7, 2015 at 3:06 AM, Byron Mann <byronos...@gmail.com> > > > > wrote: > > > > >> > > > > >> > > > > > >> > Any chance you locked down the CFIDE on the new install and you > > are > > > > >> using > > > > >> > the default listener CFIDE\websocket\ChannelListner.cfc? > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > > > > > > http://help.adobe.com/en_US/ColdFusion/10.0/Developing/WSe61e35da8d318518767eb3aa135858633ee-7ffe.html > > > > >> > > > > > >> > I haven't used websockets extensively, so I hope I'm not getting > > you > > > > off > > > > >> > track. > > > > >> > > > > > >> > > > > > >> > > > > > >> > On Tue, Jan 6, 2015 at 2:00 AM, Parul B < > > parul.sarasw...@gmail.com> > > > > >> wrote: > > > > >> > > > > > >> > > > > > > >> > > Hi, > > > > >> > > > > > > >> > > I recently upgraded to CF 11 and my chat application (which > uses > > > > >> > > Coldfusion websockets and was earlier working great with CF10 > > and > > > > >> Apache) > > > > >> > > has now suddenly stopped working. Even a basic handshake isn't > > > > >> happening. > > > > >> > > > > > > >> > > I've already tried disconnecting/reconnecting the CF > connector. > > > > >> > > > > > > >> > > Any pointers in this regard (if anyone has come across this > > issue > > > > >> after > > > > >> > > upgrading to CF11) would be highly appreciated. > > > > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > > > > > > > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359922 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
