Why do we have Gateway Timeouts on scaled out Azure App Services?
Our scenario: We have a simple client server architecture where a PWA is using our Azure Web Service as the backend. The backend has scaling out enabled.
We have this setup for years and it worked well.
Azure App Service: Is it possible to know backend compute details for App service
Is there a way to know where the app service is deployed to (like the VM/Backend details), I wanted to prove : when an app service is deployed using non-premium pricing tier and Zone redundancy disabled, All the instances (in my case the instance count: 3) will go to same AZ.
Problem with network bandwidth of Azure App Service (very slow uploads)
My App Service (A) sends a POST request that contains a base64 encoded file to App Service B . I understand that this may seem strange, but it is needed in this case. App Service B uploads it to a Blob Storage and then returns a response. The size of the file is between 40-80mb.
Azure App Service communicating with another App service deployed in a different region
I am doing a test project on azure. I have 4 app services deployed. All in different regions, all free tier.
Occasionally getting a 403 error in App Service, making it inaccessible
all. I’m currently using App Service, and sometimes I encounter sudden 403 errors. During these incidents, some users can still access the service, while others cannot. Those who cannot access it find that they can usually do so again after waiting about 3 to 20 minutes.
Azure Web App – How to get connection string into Spring web from Connection strings
I have a App service spring web app (Not Azure spring Apps).