每个闪光上传者都会给出不好的进度值 [英] Every flash uploader giving bad progress values
问题描述
在不正常的机器上，进度事件（或者回调情况可能是）报告上传太快了。它正在进步9或10MB / s左右，而不是实际正在进行的50或60kb / s。进度条填满非常快，然后不再触发进度事件。几分钟后，完成事件将在上载实际完成时触发。
我必须强调，即使报告的进度非常正常错误的。
进度事件报告正确的文件大小，但上传的报告数量通常太高，看起来总是2 ^ 16（65536）。
我只在Windows XP的Firefox 3.5上遇到这个问题，所有这些问题都有Flash 10的各种版本。
有没有人听说过这样的事情，或者有什么想法发生了什么事情？
的bug报告，但希望这里有人有一些以前的经验。）
原来是AVG代理要求。就Flash而言，它非常快速地上传到AVG。然后AVG继续在后台上传。
The file upload script I wrote early last year for an internal website has been misbehaving oddly on a number of machines. On some machines it consistently works fine, on others it consistently misbehaves. I am having exactly the same problem with YUI Uploader, SWFUpload (2.2 and 2.5a), and Uploadify.
On the misbehaving machines, the progress event (or callback as the case may be) is reporting the upload going far too quickly. It is progressing around 9 or 10MB/s, instead of the 50 or 60kb/s that is actually going on. The progress bar fills up very quickly, and then no more progress events are triggered. A few minutes later the completion event will trigger when the upload is actually done.
I must emphasize that the file upload does proceed normally, even though the progress being reported is very wrong.
The progress events are reporting a correct file size, but the reported amount uploaded is usually way too high, and it appears that it is always a multiple of 2^16 (65536).
I'm only having this problem with Firefox 3.5 on Windows XP, all of which have various subversions of Flash 10.
Has anyone heard of this happening, or have any idea what is going on?
(I'm off to go file a number of bug reports, but hopefully someone here has some previous experience with this.)
Turns out it was AVG that was proxying the requests. As far as the Flash was concerned it was uploading it very very quickly... into AVG. AVG then proceeded to upload in the background.
这篇关于每个闪光上传者都会给出不好的进度值的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
