App Service突然开始使用块编码进行响应，而之前使用Content-Length标头进行响应 [英] App Service suddenlt started to respond with Chunked encoding where it used to response with Content-Length header

问题描述

你好，

截至昨晚，其中一个我们的地理位置均衡的应用程序服务开始以Transfer-Encoding:Chunked进行响应，而过去通常不使用分块编码来进行响应 (又称为Content-Length响应标头).

As of last night, one of our geo balanced App Services started to respond with Transfer-Encoding: Chunked whereas it used to respond without chunked encoding (aka with a Content-Length response header).

我们有两个App Services.一个在美国，另一个在欧盟地区.它们都运行完全相同的代码.美国的App Service仍能按预期进行响应 (未分块)，但欧盟的App Service自昨晚起开始返回分块的响应.

We have two App Services. One in the US and the other in the EU region. They both run the exact same code. The App Service in the US still responds as expected (not chunked), but the App Service in the EU started to return chunked responses since last night.

是否有一种方法可以强制App Service发送的响应没有分块吗?

最好的问候，
埃里克(Erik)

Best regards,
Erik

推荐答案

简短更新.我刚刚在美国和欧盟创建了NEW App Services，并且欧盟实例返回的响应是分块的，美国是未分块的.因此，在美国和欧盟托管服务的行为肯定有所不同！

A short update. I have just created NEW App Services in both the US and the EU and the EU instance returns responses as chunked and the US as non-chunked. So hosting a service in the US en EU are definitely behaving differently!

这篇关于App Service突然开始使用块编码进行响应，而之前使用Content-Length标头进行响应的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！