|
Rank: Member Groups: Member
Joined: 10/17/2008 Posts: 20
|
Hi.. We are experiencing issue in AjaxUploader Control
We have other dll in <httpModules> Section of the Web.Config file as shown below.
<httpModules> <add type="DllName.CookielessPostFixModule, NHRDllName" name="CookielessPostFixModule" /> </httpModules>
It seems that when httpmodules has this dll then the Ajaxuploader control is not working.
I added EO.Web dll in the <httpModules> section as shown below but the issue still persist
<httpModules> <add type="DllName.CookielessPostFixModule, NHRDllName" name="CookielessPostFixModule" /> <add name="EOWebRuntime" type="EO.Web.Runtime,EO.Web" /> </httpModules>
If I comment out the <httpModules> section then the control is working fine, but then our application has an issue as that is the core part of our application.
so please let us know what will be the solution for this?
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi, That is very normal. The uploader needs to read the HTTP request form data. It checks the header first, if it sees it is an upload from us, it will invoke our server side handler to stream the data instead of reading the whole request data into memory. When you have another HTTP module that also checks the request form data, that form data would usually read the whole form data into memory first (because most HttpModule relies on HttpRequest.Form property, which reads the whole form data, including any file data in the request into the memory). As a result, by the time it reaches our uploader, all data has already been read by the other module and nothing else is left. You can try to add our module into your httpModule list before the other module and see if it helps. You can find details about this at here: http://www.essentialobjects.com/ViewDoc.aspx?t=InstallationAndDeployment%2fwebconfig.htmlIf that does not help, then you may need to look into the source code of CookielessPostFixModule and see if you can avoid accessing Request.Form. Thanks!
|
|
Rank: Member Groups: Member
Joined: 10/17/2008 Posts: 20
|
We can't avoid accessing Request.Form as it is needed for the application, is there any other solution? That's the core part of our application so we can't avoid it. is there any way Eo.Web dll avoid it?
Is there any way I can call Eo.WEB's Support team and get the solution as we want to go live with our application and this section is restricting it.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi,
You may wish to read our previous reply again. The key is that you can not take the data away before it reaches our uploader. You are putting our module after your module, which obviously will not work.
We do not provide phone support. In fact even if we could, I do not believe there is anything more can be done over the phone. We have clearly explained the situation and if none the workaround works, you may just have to rework your code. The bottom line is nobody should take the data away from the uploader in order for it to function. When the data has been taken away, the uploader stops working. It's really as simple as that. Sorry about that!
Thanks
|
|
Rank: Member Groups: Member
Joined: 10/17/2008 Posts: 20
|
I tried putting your module (eo.web) before our Module which didn't work.
I tried the following configuration which didn't help.
Do you know why? is there any other configuration missing?
<httpModules> <add name="EOWebRuntime" type="EO.Web.Runtime,EO.Web" /> <add type="DllName.CookielessPostFixModule, DllName" name="CookielessPostFixModule" /> </httpModules>
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi,
I am not sure what other options are available except for reworking your code for CookielessPostFixModule. The situation as I understand is, CookielessPostFixModule accesses Request.Form, which broke the uploader. And the following is true based on the information you provided:
1. When you access Request.Form on all requests, it breaks. This is the current situation; 2. If you do not access Request.Form at all, it works. This is based on your report that if you take the module out, everything works;
The only solution I can think of is to change the module so that it only access Request.Form when the request is not from the uploader. That way you are leaving data for the uploader unchanged. I believe you can access HttpRequest.Url to check whether the request Url is eo_web.ashx. If it is eo_web.ashx, you should not touch it. All uploader related requests go through eo_web.ashx.
Please note that we offer no guarantee for this and we will not troubleshoot your code. As you can understand, the product only work when certain requirements are met, we will do our best to help you to understand what those requirements are and why they are needed, but we will not be responsible for locating the offending code, properly configuring your application or guarantee you a solution even if the requirements are not meet. Those will be always your responsibilities.
Thanks
|
|