|
|
Rank: Member
Groups: Member
Joined: 6/3/2009
Posts: 27
|
We just switched from a single web server to a web farm. My TempFileLocation is a path on the web server itself, which is now causing problems when the request switches to another web server mid-upload on larger uploads.
Aside from changing the TempFileLocation to a common path on a single server, is there a workaround for this? Can I intercept the file stream and save to a database?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
The only other way is to configure your Web Farm to make sure you never switch a user from one server to another server in the middle of a session. As soon as you switch user mid-session, you will need to change TempFileLocation to a common path on a single server.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/3/2009
Posts: 27
|
OK, another question .. is there a way to specify the IP address to direct all requests from the AJAXUploader, rather than having it assume that it's the same server on which the page currently is running?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
No. You can't do that. As we have already mentioned in our previous reply, really the only option is to set your Web Farm not to switch user in the middle of a session.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/3/2009
Posts: 27
|
There's no way to "set our web farm to not switch the user in the middle of a session", it simply doesn't work that way. We also can't put a 3rd server in place that both web servers can save files to without compromising security.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
In that case I guess we have reached the dead end here. We are not aware of any other options.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/3/2009
Posts: 27
|
We’re using the standard Microsoft web farm approach. How would you configure a page such that the client would stay on one server (not have the DNS resolution of www.sitename.com expire and re-query DNS with no guarantees on the response)?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
I wish I could help you on that. But those are beyond our scope of expertise. We support our product so we can only tell you what the options are from the controls' point of view and we generally do not go beyond the product. For example, we can tell you that you can use a shared location but by no mean that means we will give you step by step instructions on how to set that up for all different version of Windows under all different possible circumstances. We are not able to do that not only because we can not afford to, but also because we are not expert on Windows security either. Thus I would suggest you to seek other help if you still have any questions on this issue.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/3/2009
Posts: 27
|
Last thing I'll say .. what I'm suggesting isn't something that's really related to Windows security, but actually something directly controllable by your control. You may not expose a property for it, but it's something you could incorporate in any future releases.
Specifically, if I were to create my own HTML page with a file upload, it would look something like this:
<form name="form1" method="post" action="WebForm1.aspx" id="form1" enctype="multipart/form-data">
Note the "action" attribute, which I can specify to any target I want. I'm sure your control is doing likewise, though probably with the XmlHTTPRequest() or something along those lines, but same premise. If you were to expose that "action" attribute as a property, I could instruct all of my uploads to go to a specific web server in my web farm. Just a suggestion for future releases. Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
Thank you very much for your suggestion. We understand the circumstance and the suggestion seems to make sense. We will definitely look into it and see what we can do in the future release. However please keep in mind that the internal work of the uploader is more complicated than a simple file post so we can not guarantee that it will be implemented the way you recommended, or whether it will be implemented at all at this time.
Thanks!
|
|