
| Key: |
CIB-1439
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Daniel Ostermeier
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 24/Apr/08 03:11 AM
Updated: 25/Apr/08 02:43 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
2.0.5,
1.2.52
|
|
|
Depending on one's point of view, this may or may not be a "bug," although it can lead to a lot of frustration.
When downloading artifacts from Pulse, the browser (IE, Firefox, Safari) displays a progress message saying, "x Kbytes downloaded of <unknown>". Progress indicators like this aren't very useful because one has no way of knowing how much more time the download will take. Given that we have many artifacts over 100 MB and we often copy them over long-distance networks, it would be nice for the progress indicators to work; then we'd see number of bytes, percent complete, average speed, and time remaining.
I believe this occurs when the HTTP header initiating the transfer contains a "content-length" field equal to zero. Setting it to the correct file size, which is known when the transfer is begun, would theoretically correct the problem.
|
|
Description
|
Depending on one's point of view, this may or may not be a "bug," although it can lead to a lot of frustration.
When downloading artifacts from Pulse, the browser (IE, Firefox, Safari) displays a progress message saying, "x Kbytes downloaded of <unknown>". Progress indicators like this aren't very useful because one has no way of knowing how much more time the download will take. Given that we have many artifacts over 100 MB and we often copy them over long-distance networks, it would be nice for the progress indicators to work; then we'd see number of bytes, percent complete, average speed, and time remaining.
I believe this occurs when the HTTP header initiating the transfer contains a "content-length" field equal to zero. Setting it to the correct file size, which is known when the transfer is begun, would theoretically correct the problem.
|
Show » |
|