JAP WS on OpenShift fail to work

GoogleCodeExporter commented 8 years ago

JAP WS on OpenShift fail to work since yesterday.

Original issue reported on code.google.com by Fight4Fu...@gmail.com on 6 Jan 2013 at 4:59

GoogleCodeExporter commented 8 years ago

Update from OPENSHIFT:
There is one more known complication. When using our preview-deployment of 
WebSockets with HTTPS and WSS protocols, you will face self-signed certificate. 
That is because this environment is only temporary to give you insight into 
upcoming features. Once we move the new routing layer to standard ports 80 and 
443, i.e. we move WebSockets support into production, the certificates used 
will be signed and valid as they are with current deployment.

We need to configure JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT with the self-signed 
certificate.
1) download the self-signed certificate
- open FIREFOX
- open https://XXX-YYY.rhcloud.com:8443
- click I UNDERSTAND THE RISKS
- click ADD EXCEPTION
- click VIEW
- click DETAILS
- click EXPORT
- open JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT
- click SAVE
2) configure JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT
- REMOTE_PROXY_SERVERS/CERTIFICATE/AUTHENTICATION/FILE = XXX.YYY.rhcloud.com

Original comment by jeroen.v...@gmail.com on 6 Jan 2013 at 11:02

Attachments:

GoogleCodeExporter commented 8 years ago

After configure JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT with the self-signed 
certificate,it shows certificate ok,but JAP WS on OpenShift still fail to work.

Original comment by Fight4Fu...@gmail.com on 6 Jan 2013 at 1:28

GoogleCodeExporter commented 8 years ago

OPENSHIFT websockets support is experimental (so not stable yet).
The last 2 days JAP did not work on OPENSHIFT, but now I do not have any 
problems.
Can you do a new test?

Original comment by jeroen.v...@gmail.com on 8 Jan 2013 at 1:16

GoogleCodeExporter commented 8 years ago

JAP on OpenShift works now,thx!

Original comment by Fight4Fu...@gmail.com on 9 Jan 2013 at 11:26

felixlu / jap

JAP WS on OpenShift fail to work #11