Default ExecutionTimeout in asp.net is 110 seconds. This doesn't normally cause any issues, but in regards to video playback its possible, that the videoplayer insists on downloading a videofile in a single request, throttling the speed to the rate of movie playback.
This means that ie. a 5 min movie will take roughly 5 minutes to download, and suddenly you'll have a Timeout Exception.
Since its possible to set ExecutionTimeout for specific files, C1 should include a setting for the ShowMedia handler to allow higher timeouts.
Comments: ** Comment from web user: mawtex **
This means that ie. a 5 min movie will take roughly 5 minutes to download, and suddenly you'll have a Timeout Exception.
Since its possible to set ExecutionTimeout for specific files, C1 should include a setting for the ShowMedia handler to allow higher timeouts.
Comments: ** Comment from web user: mawtex **
Add the following block to ~/web.config's <configuration />
```
<location path="Renderers/ShowMedia.ashx">
<system.web>
<!-- allow media streaming to take up to 15 minutes -->
<httpRuntime executionTimeout="900"/>
</system.web>
</location>
```
I haven't tested it, but it should work and our media render handler do seem to be hit by this location element.
I'm converting this to a feature request. Should we ship with this by default? I guess we should.