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
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
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
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
when you upgraded CF, are you sure the CFIDE got upgraded as well. If you
have it in a non standard place then this would not have happened.
during installation it would have verified the path it was using.
are you using the default one at cfinstall\ cfusion\wwwroot\cfide, if not
then try using
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
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
Maybe a missing CF Mapping for the custom listener path? So does something
like createObject(component, 'myPath.myCustomListener') work?
You mentioned an upgrade, is CF 10 still running on the server? Maybe a
port conflict if that's the case. I would check all the CF 11 logs to see
if there
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
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
10 matches
Mail list logo
