You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ocelot is an API Gateway that also runs on ASP.
Ocelot是一个API网关,也运行在ASP上。
NET Core.
净的核心。
A key difference between API Gateways and general Reverse Proxies is that the former tend to be message based whereas a reverse proxy is stream based.
API网关和一般反向代理之间的一个关键区别是,前者倾向于基于消息,而反向代理是基于流的。
That is, an API Gateway will typically buffer every request and response message to be able to perform transformations.
也就是说,API网关通常会缓冲每个请求和响应消息,以便能够执行转换。
This is fine for an API Gateway but not suitable for a general reverse proxy performance wise nor for responses that are chunked-encoded.
这对于API网关很好,但不适合一般的反向代理性能,也不适合分块编码的响应。
See Not Supported Ocelot docs.
参见不支持的Ocelot文档。
The text was updated successfully, but these errors were encountered:
https://github.com/ProxyKit/
Ocelot is an API Gateway that also runs on ASP.
Ocelot是一个API网关,也运行在ASP上。
NET Core.
净的核心。
A key difference between API Gateways and general Reverse Proxies is that the former tend to be message based whereas a reverse proxy is stream based.
API网关和一般反向代理之间的一个关键区别是,前者倾向于基于消息,而反向代理是基于流的。
That is, an API Gateway will typically buffer every request and response message to be able to perform transformations.
也就是说,API网关通常会缓冲每个请求和响应消息,以便能够执行转换。
This is fine for an API Gateway but not suitable for a general reverse proxy performance wise nor for responses that are chunked-encoded.
这对于API网关很好,但不适合一般的反向代理性能,也不适合分块编码的响应。
See Not Supported Ocelot docs.
参见不支持的Ocelot文档。
The text was updated successfully, but these errors were encountered: