月初 AWS 宣布 CloudFront 支援 HTTPS record,號稱可以加速 HTTPS 連線速度:「Boost application performance: Amazon CloudFront enables HTTPS record」。
這邊提到的加速主要來自於 HTTP/3,但傳統的作法會需要先用 TCP 的 HTTP/2 或是 HTTP/1.1 連線,在看到 Upgrade header 後才會用 HTTP/3。
而 HTTPS record 目前最大的用途是讓瀏覽器在 DNS query 時就知道可以用 HTTP/3,不需要透過 Upgrade header 得知,像是 www.google.com 就有 HTTPS record:
$ host -t https www.google.com www.google.com has HTTPS record 1 . alpn="h2,h3"
不過 HTTP/3 是否比較快還有爭論,加上遇到 firewall 的 fallback 機制,說「boost」有點微妙,不過就當作宣傳詞吧... 至少 HTTP/3 發明的陣營是這樣宣傳的。
但 AWS blog 這篇用到的 CloudFront 看起來都沒打開啊:
$ curl -s https://aws.amazon.com/blogs/networking-and-content-delivery/boost-application-performance-amazon-cloudfront-enables-https-record/ | grep -io '[0-9a-z]*\.cloudfront\.net' | sort -u | xargs -n1 host -t https d1d1et6laiqoh9.cloudfront.net has no HTTPS record d1fgizr415o1r6.cloudfront.net has no HTTPS record d1hemuljm71t2j.cloudfront.net has no HTTPS record d1le29qyzha1u4.cloudfront.net has no HTTPS record d1oqpvwii7b6rh.cloudfront.net has no HTTPS record d1vo51ubqkiilx.cloudfront.net has no HTTPS record d1yyh5dhdgifnx.cloudfront.net has no HTTPS record d2908q01vomqb2.cloudfront.net has no HTTPS record d2a6igt6jhaluh.cloudfront.net has no HTTPS record d2cpw7vd6a2efr.cloudfront.net has no HTTPS record d36cz9buwru1tt.cloudfront.net has no HTTPS record d3borx6sfvnesb.cloudfront.net has no HTTPS record d3ctxlq1ktw2nl.cloudfront.net has no HTTPS record d3h2ozso0dirfl.cloudfront.net has no HTTPS record d7umqicpi7263.cloudfront.net has no HTTPS record dftu77xade0tc.cloudfront.net has no HTTPS record dgen8gghn3u86.cloudfront.net has no HTTPS record dk261l6wntthl.cloudfront.net has no HTTPS record
想要找個 CloudFront 有 HTTPS record 的看一下,發現好像都沒找到... 反倒是發現 CloudFront 的 distribution hostname 長度有變?
另外是看文章時意外覺得不太對,發現是這篇介紹文章裡面用的圖片出現了 Comic Sans?(Comic Neue?)

唔,滿滿的槽點...




