|
|
Rank: Member
Groups: Member
Joined: 9/27/2009
Posts: 10
|
I'm using the upload control and uploading files is EXTREMELY slow on our test server. It works fine from my dev machine so I'm sure it has something to do with the server config.
I'm testing with a plain page (nothing on it except upload):
<eo:AJAXUploader runat="server" id="AJAXUploader1" Width="400px" TempFileLocation="~/eo_upload" MaxDataSize="30000">
</eo:AJAXUploader>
Sometimes it times out when uploading but usually it just takes a long time (5 minutes for a 1MB file). The test server is on the local network and has plenty of resources. The file does get uploaded so it is not permissions. It is an IIS 6 box.
I already did the troubleshooting suggested in help and what I could find on google:
- disable trace
- added: <requestLimits maxAllowedContentLength="100000000"/>
- increased the request size
Anyone have any ideas?
Thanks,
Amit
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
This is not normal. Please try two things:
1. Put the uploader in a blank page with nothing else and see if it works;
2. Try a standard HTML file input element or standard ASP.NET FileUpload control and see it works;
If #2 works but #1 still doesn't, we will need to access the page to see if we can see the same problem here. If the same problem occurs, we can try to analyze the HTTP packages and see if we can find anything.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/27/2009
Posts: 10
|
I tried that last night and both were still horribly slow.
However, if I upload from the internal URL instead of the public URL it was much faster, leading me to believe that perhaps it is a firewall issue.
When I try it from an outside machine on the public URL it works fine also.
At this point I'm not sure if its an issue to be concerned about.
One thing I noticed...on IE8 when I browse for a file, it shows "C:\fakepath\<filename>" no matter where the file is located. It stil uploads fine but why is it showing that?
|
|
Rank: Member
Groups: Member
Joined: 9/27/2009
Posts: 10
|
FYI, "FAKEPATH" does not show with the .net fileupload control.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
AmitM wrote:I tried that last night and both were still horribly slow.
However, if I upload from the internal URL instead of the public URL it was much faster, leading me to believe that perhaps it is a firewall issue. Yes. It could be that. AmitM wrote:One thing I noticed...on IE8 when I browse for a file, it shows "C:\fakepath\<filename>" no matter where the file is located. It stil uploads fine but why is it showing that? That's an IE 8 security feature. MS realized (or decided) that when a user wants to upload a file, they really meant to give you the file name and file contents, not the full file path. In another word, where the file really resides on user's local computer should be considered sensitive and kept as secret, thus not be sent to the server. In order to be compatible with old versions, MS decided to always send "fakepath" as the file path. This behavior is usually kept transparent to the user. However when our script tries to read the file path, we get "fakepath" instead of the real path. Due to certain implementation details, we need to read and display this path to the user. It ends up with user seeing what's really being sent to the server. Unfortunately we are not aware of any workaround to this at this time. Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/27/2009
Posts: 10
|
I saw this in another post, is it still a valid work around? eo_support wrote:To avoid user from getting confused by seeing the "fakepath" file name, you can customize the uploader to hide the text box part completely. In order to do so you will need to connect an uploader with a toolbar button. Your user would then select the toolbar button to browse and upload a file. You can find a working example about this feature at here: http://demo.essentialobjects.com/Default.aspx?path=AJAXUploader\uploader_toolbar
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Yes. It is. But it will be a single upload "button" for you. There is no way for you to show the real path to the user as the standard ASP.NET or HTTP upload control does.
Thanks
|
|