当要求超过10 MB时
我有问题,因为当我尝试使用Azure Redis Cache配置Azure API管理时该请求超过9/10MB,密钥未写入REDIS缓存。 我已经检查了问题肯定是在API管理的一边,因为如果我直接从控制台应用程序中写入缓存,则所有数据甚至是为50MB编写的。
我在API管理方面的政策: 入站
<cache-lookup vary-by-developer="false" vary-by-developer-groups="false" allow-private-response-caching="true" must-revalidate="false" downstream-caching-type="public" caching-type="external" />
出站,
<cache-store duration="1000" cache-response="true" />
如果我将下游式型类型更改为non
I have a problem because when I try to configure Azure Api managment with Azure Redis Cache my data does not always get saved, if the request "GET" is up to 9MB everything is okey the key and its value goes to the Redis cache but if the request exceeds 9/10MB the key is not written to the Redis cache.
I have checked that the problem is definitely on the side of the api management because if I write to the cache directly from the console application, all the data is written even for 50MB.
My policy in API management :
Inbound
<cache-lookup vary-by-developer="false" vary-by-developer-groups="false" allow-private-response-caching="true" must-revalidate="false" downstream-caching-type="public" caching-type="external" />
outbound
<cache-store duration="1000" cache-response="true" />
If I change downstream-caching-type to none then request to 9MB not working only request max to 2MB
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
如 Silent 将其添加为社区Wiki答案,以帮助可能面临类似问题的社区成员。
按照 api管理限制,最大缓存响应响应大小为2MB。
您可以按照最佳实践关于如何处理较大响应大小的最佳实践:
对大量小值的应用优化您的应用程序,而不是一些大值。
增加VM的大小以获得更高的带宽功能。
增加应用程序使用的连接对象的数量。
As commented by silent, adding it as a community wiki answer to help community members who might face a similar issue.
As per API Management limits, maximum cached response size is 2MB.
You can follow the best practices on how to handle a larger response sizes:
Optimize your application for a large number of small values, rather than a few large values.
Increase the size of your VM to get higher bandwidth capabilities.
Increase the number of connection objects your application uses.