简体   繁体   English

如果浏览器不支持 quic,http3/quic 是否会退回到 tls 1.2?

[英]Does http3/quic fall back to tls 1.2 if the browser doesn't support quic?

Even after lots of googling, I'm pretty naive about quic.即使经过大量的谷歌搜索,我对 quic 还是很天真。 I'm specifically looking into lucasclemente/go-quic.我正在专门研究 lucasclemente/go-quic。

Should quic servers use 443? quic 服务器应该使用 443 吗? If so, will it fallback to http2 & tls 1.2?如果是这样,它会回退到 http2 和 tls 1.2 吗? I'm speaking generally.我说的一般。 Not for that specific go package.不适用于特定的 go package。 But if you have specifics for that go package, that would be great.但是,如果您有 go package 的详细信息,那就太好了。

Yes, I realize quic is still young and not necessary yet.是的,我意识到 quic 还很年轻,还没有必要。 I'm simply curious and couldn't find that specific answer.我只是好奇,找不到那个具体的答案。 Thanks!谢谢!

Quic servers can use any port they want; Quic 服务器可以使用他们想要的任何端口; 443 is often used, but this is not necessary at all. 443经常被使用,但这根本没有必要。 Note we're talking about UDP ports, not TCP ports.请注意,我们谈论的是 UDP 端口,而不是 TCP 端口。

A QUIC server cannot fallback to HTTP2 or TLS 1.2, because if the client sends a QUIC request, the server can only respond with a QUIC response. QUIC 服务器不能回退到 HTTP2 或 TLS 1.2,因为如果客户端发送 QUIC 请求,服务器只能以 QUIC 响应进行响应。 If the browser doesn't support QUIC, it will not send a QUIC request in the first place, so there is no issue at all.如果浏览器不支持QUIC,一开始就不会发送QUIC请求,所以完全没有问题。

I think you are assuming that a QUIC server runs (or can run) on the same port as HTTPS and therefore has to generate either a QUIC or an HTTPS response;我认为您假设 QUIC 服务器在与 HTTPS 相同的端口上运行(或可以运行),因此必须生成 QUIC 或 HTTPS 响应; this is not the case, as QUIC is running over UDP, not over TCP (like HTTP and HTTPS do).情况并非如此,因为 QUIC 在 UDP 上运行,而不是在 TCP 上运行(如 HTTP 和 Z0E832363F9A4B04FD1)。 TCP ports and UDP ports are different address spaces, so one can run an HTTPS server on tcp port 443 and simultaneously run another QUIC server on udp port 443. TCP ports and UDP ports are different address spaces, so one can run an HTTPS server on tcp port 443 and simultaneously run another QUIC server on udp port 443.

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 我们可以将请求表单服务器发送到客户端并通过 quic/http3 获得响应吗? - Can we send request form server to client and get response through quic/http3? 传输选项以确保Net / http客户端通过TLS 1.2连接 - Transport options to ensure net/http client connect via TLS 1.2 如何从 Chrome 访问 github.com/lucas-clemente/quic-go 服务器? - How do I access a github.com/lucas-clemente/quic-go server from Chrome? golang TLS是否支持IE8? - Does golang TLS support IE8? curling http-server 没问题,但浏览器不起作用 - curling http-server is ok but with the browser doesn't work 无法在 quic golang appengine 中充分增加接收缓冲区大小(原为:208 kiB,想要:2048 kiB,获得:416 kiB) - Failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB) in quic golang appengine Docker 是否支持重定向 HTTP? - Does Docker Support Redirect HTTP? 如何将 TLS 1.2 与 MySql Go 驱动程序一起使用? - How to use TLS 1.2 with MySql Go Drivers? golang tls.Config CiperSuites不限制客户端身份验证 - golang tls.Config CiperSuites doesn't restrict client auth Google App Engine的Google Cloud SQL(第2代)出现“请求TLS但服务器不支持TLS”错误? - “TLS requested but server does not support TLS” error with Google Cloud SQL (2nd generation) from Google App Engine?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM