{"type":"rich","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fwww.shigemk2.com%2Fentry%2F2025%2F07%2F14%2F234516\" title=\"cluster.proto http2_protocol_options - by shigemk2\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","width":"100%","version":"1.0","published":"2025-07-14 23:45:16","image_url":null,"title":"cluster.proto http2_protocol_options","categories":["Envoy"],"author_url":"https://blog.hatena.ne.jp/shigemk2/","url":"https://www.shigemk2.com/entry/2025/07/14/234516","height":"190","blog_title":"by shigemk2","author_name":"shigemk2","blog_url":"https://www.shigemk2.com/","provider_url":"https://hatena.blog","description":"Even if default HTTP2 protocol options are desired, this field must be set so that Envoy will assume that the upstream supports HTTP/2 when making new HTTP connection pool connections. Currently, Envoy only supports prior knowledge for upstream connections. Even if TLS is used with ALPN, http2_proto\u2026","provider_name":"Hatena Blog"}