<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HTTP/JSON on PlumePHP</title><link>https://plumephp.com/tags/http/json/</link><description>Recent content in HTTP/JSON on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sun, 27 Sep 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/http/json/index.xml" rel="self" type="application/rss+xml"/><item><title>gRPC网关与HTTP转码实战：Envoy gRPC-JSON转码与grpc-gateway统一接入</title><link>https://plumephp.com/grpc-gateway-transcoding/</link><pubDate>Sun, 27 Sep 2026 10:00:00 +0800</pubDate><guid>https://plumephp.com/grpc-gateway-transcoding/</guid><description>&lt;h2 id="引言"&gt;引言&lt;/h2&gt;
&lt;p&gt;微服务之间用 gRPC 通信能享受 HTTP/2 多路复用、Protobuf 二进制序列化和强类型契约的红利，但 gRPC 对浏览器与移动端并不友好：浏览器无法直接发起 gRPC 调用（需要 gRPC-Web 代理），移动端与第三方开发者更习惯 JSON over HTTP。于是团队陷入两难——维护一份 gRPC Proto 契约，再为 Web 另写一套 REST 接口？契约分裂、语义漂移、双重维护成本随之而来。&lt;/p&gt;</description></item></channel></rss>