Openshift certificate changes(maybe improves)

[GoogleCodeExporter]

What steps will reproduce the problem?
1.A few days ago,followed the README.txt steps to deploy JAP on Openshift,and 
opened https://YYY-ZZZ.rhcloud.com:8443 to download certificate then configured 
JAP_WS_LOCAL.json correctly.Everything worked. 
2.This days the famous 'connectionlost' problem appears again.Open 
https://YYY-ZZZ.rhcloud.com:8443 without any proxy,and there is no longer 
certificate risk with the certificate information that Common Name is 
*.rhcloud.com.

What is the expected output? What do you see instead?
Terminal output 'connectionlost'
Chromium output 'Error 120'

What version of the product are you using? On what operating system?
1.Remote:JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3
2.Local:JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2-TEST
3.OS:Archlinux + Xfce4.10 + Chromium

Please provide any additional information below.
My correction method is to delete the content of 
REMOTE_PROXY_SERVERS/CERTIFICATE/AUTHENTICATION/FILE,just "FILE": "".
Everything works again.
I think there is some improvement of Openshift certificate,no longer need to 
download local certificate.  

Original issue reported on code.google.com by westmin...@gmail.com on 1 Feb 2013 at 6:24

[GoogleCodeExporter]

You are correct, the certificates are updated.

Thanks for the information :)

Original comment by jeroen.v...@gmail.com on 1 Feb 2013 at 6:52