Windows Azure - frequent protocol violations with content length inconsistencies

Question

I am working on modifying an existing standalone ASP.NET web application to run on Windows Azure. I successfully deployed the application to a web role, and initially at first glance everything seemed to work fine.

However, I quickly began to notice that Javascript did not execute on many pages as I expected. Further research showed that many pages did not load completely. I used Firefox (which seems to be more forgiving) and it displays partial content, while IE just displays "Page cannot be displayed."

Running fiddler or charles. I see that protocol violations occur with content length inconsistencies (the server sets the content length response header to one value, but then does not return the full content.

The length of the returned content seems to be changing, so I could not find a link to the cover for the length of the response, or something like that. Here are some sample error messages from fiddler:

Fiddler detected a protocol violation in session # 27. Content length mismatch: The response header indicated 26,716 bytes, but the server sent 23,138 bytes.

Fiddler detected a protocol violation in session # 47. Content length mismatch: The response header is 54,444 bytes, but the server sent 32,546 bytes.

Fiddler detected a protocol violation in session # 80. Content length mismatch: The response header indicated 27152 bytes, but the server sent 18.726 bytes.

This behavior does not occur in the application when running locally using the Azure Calculation Emulator or in the original local application - this only happens when deploying to Azure.

In case this helps, the web application is an ASP.NET 2.0 application running under .NET 3.5 SP1.

Any ideas on what might cause this problem?

Answer 1

I should have tried this before, but after posting this question, I had the idea of ​​accessing the application in Azure from outside our corporate network and was surprised to find that I did not experience any of the problems described above.

Thus, this narrows the problem associated with our corporate network, which for some reason causes problems with this domain. Our IT team is still investigating the root cause, but I confirmed that this does not seem to be a problem with Azure itself.

Thanks for answers.