Hi Tim,
I am unsure whether the problem still exist - I tried to reproduce it according to information you sent us through email, but was able to upload successfully (I have just emailed you about this). But anyway, I will put my two cents into this problem. Maybe it will be helpful for someone.
In fact this problem is not necessary can be caused by missing cookies. This message appears every time when the server code tries to redirect you to some other page. When it happens, the connection established by Image Uploader is closed with HTTP code 300 (or 301, 302, etc - no matter).
Why it may happen?1. Situation described in the article Alex refers. Although you tell that it cannot happen in your case, let me outline the reason of server redirect in this scenario. It happens if you are using cookie-based authentication but that cookie under certain circumstances is invisible for IU. So when Image Uploader tries to post anything to the upload processing page, it is deemed to be logged out, and the server redirects you to the login page.
2. Your server code just calls Server.Redirect method directly. I do not thing that it is your case, because I think you would notice that.
3. Some server error occurs (for example, insufficient permissions, syntax error, some unhandled exception, or something like this) and your server is configured to redirect the user to a specific "user-friendly" error page. In this case Image Uploader may get HTTP code 300 instead of HTTP code 500. This is also strange (since ActiveX works fine), but it worth to check out. Just try to debug the server page, maybe you will find anything.
How to fix it?Well... Obviously it is necessary to check out all three points, especially the first one. I know you hate to hear about http-only cookies stuff again, but this is the most frequent reason of the problem, that's why guys recommend to take a look at it all the way. I think that the best way to understand whether the problem is in them or not is to disable http-only cookies and see whether it will work. To do it you should change appropriate web.config entry like this:
<httpCookies httpOnlyCookies="false" />
If it turned out that none of this helps, namely:
1. Upload still fails with the same error message with httpOnlyCookies = "false".
2. You do not call Server.Redirect anywhere in the Action page.
3. You do not have server-side error in this page (most likely it is not called at all, so the problem occurs before IIS passes the control into this page).
In this case we need to take a deeper look into this. What we need from you is:
- Link to your page with all necessary login information, etc.
- Information about the browser you use, etc.
- If the problem happens from time to time (e.g. if you send a certain number of files or something like this), information how to get it assuredly.
- Java console output.
I hope this helps.
Sincerely yours,
Andrew Simontsev from Aurigma Team