Simon Waight • 8/31/2012

Gone in 60 Seconds - Cloud Load Balancing Timeouts

Read Original

The article details troubleshooting an issue where AWS Elastic Load Balancer's default 60-second timeout caused problems for long-running HTTP POST requests in an Umbraco CMS setup, leading to duplicate operations. It explains the root cause, demonstrates the issue with debugging tools, and discusses why AWS imposes this limit. The author suggests software design changes, like the Post-Redirect-Get pattern, as a solution and notes that AWS can increase the timeout upon request.

0 comments
#Cloud Infrastructure #Load Balancing #Timeouts
Gone in 60 Seconds - Cloud Load Balancing Timeouts

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Using Browser Apis In React Practical Guide
Jivbcoop • 2 votes
3
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
4
Top picks — 2026 January
Paweł Grzybek • 1 votes
5
In Praise of –dry-run
Henrik Warne • 1 votes
6
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
7
Vibe coding your first iOS app
William Denniss • 1 votes
8
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
9
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes