REST API reliability challenges in Azure
For those of us that are software developers, we are accustomed to this message.
"The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. T...
Forum Discussion
I took the liberty to condense your posts into one thread, as they are all effectively about one topic (making the REST api work reliably in Azure).
JackLacava Please don't. They have entirely different root causes. A DNS failure is different than a load balancer constraint, which is different than SSL inspection client-side issues.
They are all precise infrastructure issues that are better discussed with our Support guys; so to start with, reading you've already opened tickets, I was tempted to just archive them. However, from the perspective of forum readers, who are mostly application administrators and application developers, they all originate from using the REST api in Azure and the reliability challenges that arise from that scenario - I think you understand that, considering you've effectively linked them together with that "part 1/2/3" in the title. So I thought there was the chance of a useful strategic discussion if we framed it like that. I'm really sorry if it looks harsh; I'm just trying to keep this space look more like a discussion area than a support-ticket queue.
Edit: thinking about it a bit more, regardless of the principle, I should have probably discussed it with you before taking action. Sincere apologies, I'll do that in the future.