Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GWT Comet over HTTPS on Chrome doesn't work #796

Closed
LuckyLuo opened this issue Jan 4, 2013 · 0 comments
Closed

GWT Comet over HTTPS on Chrome doesn't work #796

LuckyLuo opened this issue Jan 4, 2013 · 0 comments
Labels

Comments

@LuckyLuo
Copy link

LuckyLuo commented Jan 4, 2013

Atmosphere GWT version: 0.8
Chrome Version: 23.0.1271.97 m

GWT Comet over HTTPS on Chrome doesn't work. The connection breaks every few seconds.
But it works well over HTTP on Chrome and HTTP/HTTPS on IE and Firefox.

The https detail is list below, response status code is 200.

Request URL:https://10.11.0.64/emsgui/gwtComet?t=1EF6Z7&c=666&tr=HTTPRequest
Request Method:GET
Status Code:200 OK
Request Headersview source
Accept:application/comet
Accept-Charset:GBK,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:zh-CN,zh;q=0.8
Connection:keep-alive
Cookie:JSESSIONID=shwjev8fshow2iv8c1hzcfqf; BM_SESSION_ID=YWRtaW46a2VxNXZlYkVjZ1lLdlpWYjg2M3ZYQT09; user.name=admin; GLog=%7B%0D%20%20%20%20left%3A0%2C%20%0D%20%20%20%20top%3A0%2C%20%0D%20%20%20%20width%3A1602%2C%20%0D%20%20%20%20height%3A813%2C%20%0D%20%20%20%20priorityDefaults%3A%7B%0D%20%20%20%20%20%20%20%20Log%3A4%0D%20%20%20%20%7D%2C%20%0D%20%20%20%20defaultPriority%3A3%2C%20%0D%20%20%20%20trackRPC%3Atrue%0D%7D
Host:10.11.0.64
Referer:https://10.11.0.64/index.jsp
User-Agent:Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 Safari/537.11
Query String Parametersview URL encoded
t:1EF6Z7
c:666
tr:HTTPRequest
Response Headersview source
Cache-Control:no-cache
Content-Encoding:deflate
Content-Type:application/comet;charset=UTF-8
Server:Jetty(7.4.5.fuse20111017)

Transfer-Encoding:chunked

So, is it an known issue on version 0.8? Does this issue has been fixed? If does, which version fixes it?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants