Bug 1070317 - websocket implementation isn't working
Summary: websocket implementation isn't working
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: All
OS: All
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Mrunal Patel
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-26 15:31 UTC by JustMe
Modified: 2015-05-14 23:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-03 22:07:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description JustMe 2014-02-26 15:31:41 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 JustMe 2014-02-26 15:34:26 UTC
Description of problem: 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 JustMe 2014-02-26 15:36:15 UTC
websocket implementation isn't working in node.js
The error:
Connection Close Frame (Opcode 8, mask)
Connection Close Frame (Opcode 8)

and socket.io implementation falls back to XHR. That is very slow.

I found another example: http://chattest-debugito.rhcloud.com/

Please solve the problem. It is equal to the service being out.

Comment 3 Mrunal Patel 2014-02-26 17:50:55 UTC
Could you provide more details about your application? Also, are you using port 8000/8443 to access it?

Comment 4 JustMe 2014-02-26 19:12:20 UTC
First of all I suggest that you try to setup a simple websocket app and see if it works. If it does, pay attention if it is indeed a websocket protocol.

Sure. I use 8443 for wss connection. The same applications used to work just two days ego. (I did not change it a bit)!

I dropped this app in heroku and it works just fine.
BZW: they do not need the special ports.

To check the problem open the next link in crome: http://chattest-debugito.rhcloud.com/

Go to development tools-network-websockets and reload the page. Click on the websocket that you see and in Frames you will see the error I am speaking about.

Comment 6 openshift-github-bot 2014-02-27 19:39:41 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/fc41c1c85a4e781bd6826d5e2fd640e93b117c72
Bug 1070317: Pass original request uri to the backend.

Comment 7 JustMe 2014-02-28 08:49:14 UTC
(In reply to openshift-github-bot from comment #6)
> Commit pushed to master at https://github.com/openshift/origin-server
> 
> https://github.com/openshift/origin-server/commit/
> fc41c1c85a4e781bd6826d5e2fd640e93b117c72
> Bug 1070317: Pass original request uri to the backend.

So, I see that the "change" is pushed to master. When is the problem with openshift online will be solved?
(it seems that you need some faster way to fix problems)

Comment 11 Peter Ruan 2014-02-28 21:24:16 UTC
verified in STG by doing the following:
1. rhc app create mynodejs010 nodejs-0.10
2. rhc cartridge-add -a mynodejs010 -c mongodb-2.4
3. cd mynodejs010
4. git remote add upstream -m master git://github.com/ramr/pacman.git
5. git pull -s recursive -X theirs upstream master
6. git push
7. open app in Chrome browers and view it with the Developer's tool network tab.
8. saw the websocket request.

Comment 14 JustMe 2014-03-03 22:07:03 UTC
It is working now. Thanks.
Tolik


Note You need to log in before you can comment on or make changes to this bug.