在大型网站上迁移到HTTPS的最佳和最新方式是什么？ [英] What is the best and current way to move to HTTPS on a large website?

问题描述

观看YouTube上的无处不在的HTTPS

他们认为HTTPS和SPDY的组合将比通过HTTP提供网页/资产更快，但随后阅读 SPDY已死。长期HTTP / 2 以及与HTTP2支持有关的方式我想知道是否要移动一个大型网站我正在努力完成HTTPS，因为最终它会因为执行性能比较而变慢测试（加载的DOM内容需要两倍的时间来加载）。我还读过浏览器正在放弃对SPDY的支持。

From watching HTTPS everywhere on YouTube they suggest that HTTPS and SPDY combined will be quicker than just serving web pages/assets over HTTP but then since reading SPDY is Dead. Long Live HTTP/2 and what with with HTTP2 support being a way off I am in two minds as to whether to move a large site I'm working on to HTTPS entirely as ultimately it will be slower since doing perf comparison tests (the DOM content loaded took twice the time to load). I also just read somewhere that browsers are dropping support for SPDY.

SPDY的状态是什么，我应该等到HTTP2，直到我提倡将所有内容移至到处都是HTTPS？我应该接受性能下降吗？

What is the state of SPDY and should I just wait until HTTP2 until I advocate moving everything to HTTPS everywhere? Should I accept the performance hit?

推荐答案

SPDY肯定会死，现在HTTP / 2是官方规范。

SPDY is definitely dying, now that HTTP/2 is an official specification.

Firefox和Chrome已经支持HTTP / 2，服务器开始部署它而不是SPDY - 谷歌，Twitter等。随着IE 11的推出，Internet Explorer支持将很快到来。

Firefox and Chrome already support HTTP/2, and servers start to deploy it instead of SPDY - Google, Twitter, etc. Internet Explorer support will arrive soon with IE 11.

HTTP / 2绝对是获得动力，未来将是HTTP / 2和TLS。

HTTP/2 is definitely gaining momentum, and the future will be on HTTP/2 and TLS.

您不应该等待获取HTTP / 2，因为它已经在这里。

You should not wait for HTTP/2, because it's already here.

关于性能打击，通常的建议是基准测试，但是e证明HTTP / 2 over TLS比HTTP / 1.1优于TLS，并且可能与明文HTTP / 1.1相当 - 如果不是更好 - 取决于具体情况。

About the performance hit, the usual recommendation is to benchmark, but there is evidence that HTTP/2 over TLS is much better than HTTP/1.1 over TLS, and possibly comparable - if not better - than cleartext HTTP/1.1, depending on the case.

这背后的原因是HTTP / 2执行的一些优化，例如多路复用，报头压缩和资源推送，这些都是HTTP / 1.1无法实现的。

Reasons behind this are a number of optimizations performed by HTTP/2 such as multiplexing, header compression and resource push, that are simply not possible with HTTP/1.1.

例如参见演示视频（免责声明，我是码头我们在2012年提供的（当时关于Jetty和SPDY，但 HTTP / 2表现相同），或 Go语言HTTP / 2演示，或 Akamai HTTP / 2演示。

See for example the demo video (disclaimer, I am a Jetty committer) we gave in 2012 (about Jetty and SPDY at that time, but HTTP/2 behaves the same), or the Go language HTTP/2 demo, or the Akamai HTTP/2 demo.

例如，使用Jetty，您可以部署Java HTTP / 2上的webapps，还有HTTP / 2上的完整PHP网站。我们自己的网站 https://webtide.com 是由Jetty在HTTP / 2上提供的WordPress。

With Jetty, for example, you can deploy Java webapps on HTTP/2, but also complete PHP websites on HTTP/2. Our own website, https://webtide.com, is WordPress served by Jetty on HTTP/2.

您现在可以转到TLS和HTTP / 2.

You can move to TLS and HTTP/2 now.

这篇关于在大型网站上迁移到HTTPS的最佳和最新方式是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！