Chrome 54无法从我的网站获得HTTPS响应; Chrome 53,Chromium,Firefox和Safari [英] Chrome 54 doesn't get HTTPS response from my site; Chrome 53, Chromium, Firefox, and Safari do

查看:156
本文介绍了Chrome 54无法从我的网站获得HTTPS响应; Chrome 53,Chromium,Firefox和Safari的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大约一周前,我的网站工作正常。自Chrome版本54以来,我无法加载它。 HTTPS请求没有得到任何回应,并显示(取消)的状态。它在Chromium,Firefox,Safari,甚至Chrome 53中都能很好地加载.Chrome的开发者工具不提供任何有用的信息 - 请参阅图片。





以下是它在Chromium中的样子:





(您会注意到第二张图片显示了子域www,这是因为,当裸域加载)



我试着修改我的服务器代码(Node,Express),在收到每个请求后打印消息,而不是甚至在我访问Chrome中的网站(54.0.2840.71(64位))时也会打印。它在我访问Chromium(53.0.2785.143(64位))时确实打印。



我甚至尝试使用不同的计算机。同样的事情 - 在Chrome中失败,在Safari中成功。



有什么可以让它表现得像这样?我不知道从哪里开始解决这个问题。

解决方案

我不太了解这种行为,但我找到了一种方法修复它在我的应用程序。我使用的是NPM模块 spdy 来代替Node的内置 https 模块通过https提供我的应用程序。切换回内置模块解决了问题。 (这是一个简单的改变 - API是兼容的。)我不知道spdy在Chrome 54中是否一直存在这个问题,但我在这个问题上浪费了太多时间,所以我将作为练习考古学家下一个挖掘这个答案。

As of about a week ago, my website was working fine. Since Chrome version 54, I can't get it to load. The HTTPS request doesn't get any response and shows a status of "(canceled)". It loads just fine in Chromium, Firefox, Safari, and even Chrome 53. Chrome's developer tools don't give any helpful information - see the image.

Here is what it looks like in Chromium:

(You'll note that the second image shows the subdomain www. That's because, when the naked domain loads properly, it redirects to the subdomain.)

I tried modifying my server code (Node, Express) to print a message upon receipt of each request, and it doesn't even print when I visit the site in Chrome (54.0.2840.71 (64-bit)). It does print when I visit in Chromium (53.0.2785.143 (64-bit)).

I even tried using a different computer. Same thing - fails in Chrome, succeeds in Safari.

What could make it behave like this? I don't know where to begin troubleshooting this.

解决方案

I don't really understand the behaviour, but I found a way to fix it in my app. I was using the NPM module spdy in place of Node's built-in https module to serve my app over https. Switching back to the built-in module solved the problem. (It's a simple change - the APIs are compatible.) I don't know whether spdy consistently has this issue in Chrome 54, but I've wasted too much time on this issue, so I will leave further investigation as an exercise for the archaeologist who next digs up this answer.

这篇关于Chrome 54无法从我的网站获得HTTPS响应; Chrome 53,Chromium,Firefox和Safari的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆