Well, this probably fixed the issue by changing some non-relative links in your browser-side Javascript handling AJAX calls to https instead of http.
I've seen instances where AJAX calls reference items that themselves call non-relative links that are on a different protocol -- meaning it calls a method to retrieve content,
store content, or update status but does so using a full URL instead of a relative path (e.g. http.open ("GET", "http://site.org/path/to/svc?"+params, true); ). It works
fine so long as it doesn't get a 302 Redirect in response, but when it does it has no way to handle a redirect response unless it's been specifically written to do so (data.redirect).
See, AJAX is interesting on the client side in that it will assign "success" to any non-error response coming back to it -- that includes a 302 Redirect. If the coder has not taken into
account the possibility of a redirect, it may fall through the error handling -- or, worse, it may call abort().
In your case, I think the situation is a little different; I can't say for sure without digging into your code, but I suspect that your application is doing an AJAX call to a method on
a regular basis (the bf8ee-presence call, maybe) that is not configured to know how to respond to a 302 and instead calls abort(). You upload some files and get successes because
your POST upload completes before the other AJAX call takes place, but get failed transfers because when abort() is called for an unrecognized response on the bf8ee-presence call
it aborts the AJAX call for the transfer too. Thus, some transfers complete, some never do.
Unsure why you're getting the error message; it could be that the behavior of a failed POST is to try again with GET... or that the browser has by then gotten another 302 and turns
the POST attempt into a GET (that's what redirects tend to do to POSTs).
Glad the stream profile fixed it for you. If you really want to see what is going on here, you should turn off the stream profile, capture an HTTPwatch of the transaction, then turn the
stream profile back on and compare the delivered files. I'd be willing to bet you're going to see some changes to downloaded Javascripts.