An application resource called Cables

83 views
Skip to first unread message

tonypm

unread,
Mar 2, 2017, 7:36:07 AM3/2/17
to Ruby on Rails: Talk
I have an application which has a resource called cables.  But after upgrading to Rails 5.0.1, I can no longer access the cables index page.

in the log I get:

Started GET "/cables" for 127.0.0.1 at 2017-03-02 12:32:04 +0000
Started GET "/cable/s"[non-WebSocket] for 127.0.0.1 at 2017-03-02 12:32:04 +0000
Failed to upgrade to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: keep-alive, HTTP_UPGRADE: )
Finished "/cable/s"[non-WebSocket] for 127.0.0.1 at 2017-03-02 12:32:04 +0000

Presumably I am getting a conflict with ActionCable routing.

Is there a way to avoid this whilst retaining my own cables resource, or am I better off completely moving my resource to another name.


Mike

unread,
Mar 9, 2017, 3:43:11 AM3/9/17
to Ruby on Rails: Talk
If you are not using ActionCable then remove it from the gem files and initialisers
Reply all
Reply to author
Forward
0 new messages