|
|
Rank: Advanced Member
Groups: Member
Joined: 8/24/2007
Posts: 130
|
Hi,
I am having a problem with the AJAXUploader timing out prematurely. Within my web application, I set an executionTimeout globally. The page which is hosting the AJAXUploader, requires a greater executionTimeout, which I set in Page_Init using Server.ScriptTimeout.
I am finding that the AJAXUploader will always time out on the value set in web.config, and not the value specified for the hosting page.
Thanks,
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
That is normal. ScriptTimeout controls the time out of the value of the current request, whereas AJAXUploader uses a separate request (uploading file does not trigger any of your page code), so your time out value has no effect on the uploader. It would make sense to be able to set the time out value separately though. So we will look into that and see what we can do.
Thanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 8/24/2007
Posts: 130
|
Thanks for that. Is it possible to give some indication as to how long this may take?
Regards
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
We understand it would be a useful feature. But we do not know whether it's possible yet, or it's possible but has other side effects. So it's too early to say that now.
Thanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 8/24/2007
Posts: 130
|
Hi,
I have tried to solve this problem by placing the page that hosts the AJAXUploader into a separate folder. This folder has a separate web.config, specifying a greater request timeout value. However, I am finding that the AJAXUploader is still timing out at the value specified in the main application web.config value. Is there anyway I can get the AJAXUploader to take the value from the second web.config?
Regards
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
Very creative solutions. :) Unfortunately we have not looked into it the detail yet, so we can not tell whether or why what works or not.
Thanks
|
|
Rank: Newbie
Groups: Member
Joined: 3/16/2009
Posts: 9
|
Hello,
Has there been any progress regarding this issue? Is there any way to override default executionTimeout setting for a specific page or specific control instance?
Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi, Have you tried to use a location element in your web.config and then set executionTimeout inside that location tag?
Code: HTML/ASPX
<location path="SomePage.aspx">
<system.web>
<httpRuntime executionTimeout="100" />
</system.web>
</location>
Thanks
|
|
Rank: Newbie
Groups: Member
Joined: 3/16/2009
Posts: 9
|
Yes, but unfortunately that didn't work.
Now I'm using global setting, but it's still not good because it's too big for most of the pages and too small for those where users actually upload something :)
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi, It's my bad. The path value for location element should be "eo_web.ashx". The uploader uploads through eo_web.ashx, not the page that contains the uploader. You may need to explicitly specify the location of eo_web.ashx in your appSettings section: http://doc.essentialobjects.com/library/1/installationanddeployment/deploy.aspxLook for "Placing eo_web.ashx at a different location" section. Thanks!
|
|