![]() Since we are concentrating on an issue with the application code, we can address the time-out issue by increasing the AAG request time-out period gradually until we can use the application and perform the request successfully. The gateway waits for the response, and if it does not receive one within the time-out period, it throws the 504 error. The cause of this error is that AAG has not received a timely response from the application server. The issue in the browser looks like this: 504 Gateway Time-Out Error What does the 504 error look like, and what is its cause?Ī user receives a 504 error in their browser when there is a long-running request related to the site accessed or some action that the user has performed in the web application. ![]() Check the AAG overview documentation for detailed explanations of its other features. Secure sockets layer (SSL/TLS) terminationĪAG has proven very useful with the increased usage of Azure resources for applications.The following features of AAG make it a practical and universally available load balancer: Azure Application GatewayĪs per Microsoft, AAG is a web traffic load balancer enabling us to manage web application traffic. This blog will explain how to resolve a 504 gateway time-out error in Azure Application Gateway (AAG) caused by an application error or performance issues. One of our previous articles, 8 Common HTTP Error Codes and Their Possible Fixes, explains a 504 gateway time-out error, its causes, and possible fixes. This error might be temporary due to heavy traffic to the website, or it might be due to a resource or request taking too much time to load. An HTTP 504 error code is sent to the browser when the request takes too long to complete. When a browser attempts to load a website, a request is typically made to a web server. BoldSign – Electronic Signature Software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |