Any way to extend the timeout on individual HTTP requests?

Try Scheduling Background or Long Running Processes 

 Matt you could combine this with community.telligent.com/.../scheduledfile-ui-component

which can be used to show progress 

Sounds good.. I'll see what I can put together. Thanks for your replies Mathew & Karl.. I really appreciate it!

BTW, I think I have another alternative.. I added a helper script API with the following C# code;

[Documentation("Set the timeout on a particular request (overriding the default, which is 110 sec)")]
public void SetRequestTimeout(int Timeout)
{
	var context = System.Web.HttpContext.Current;
	if (context == null) return;
	context.Server.ScriptTimeout = Timeout;
}

We can then add this to the top of any widget worker code that is going to take a little bit longer than usual;

$e14_utils.SetRequestTimeout(180)

In my limited testing it looks like it's done the trick; I see to see how it behaves when it hits our Azure environments later today.

When I get time I'll look into the other suggestions you had

BTW, I think I have another alternative.. I added a helper script API with the following C# code;

[Documentation("Set the timeout on a particular request (overriding the default, which is 110 sec)")]
public void SetRequestTimeout(int Timeout)
{
	var context = System.Web.HttpContext.Current;
	if (context == null) return;
	context.Server.ScriptTimeout = Timeout;
}

We can then add this to the top of any widget worker code that is going to take a little bit longer than usual;

$e14_utils.SetRequestTimeout(180)

In my limited testing it looks like it's done the trick; I see to see how it behaves when it hits our Azure environments later today.

When I get time I'll look into the other suggestions you had