Bear with me here...this should *never* be done, but....
On a fake, long-running page (a la Thread.Sleep(180000) - yes, that's 3:00), there seems to be no way to get past the 1.5 ~ 2 minute mark before receiving an HTTP 504 (Gateway Timeout) error. I've tried both system.web\httpRuntime\executionTimeout element as well as the IIS 7.0 Connection Limit Timeout (default, 120 seconds).
Is there a published maximum request time that the Azure load balancer(s) will allow?
In case you're wondering, this is a project involving porting a legacy app that had such timeouts...I'm trying to make the case for changing to a deferred pattern (submit job, poll for status).
Cheers...