Closed Bug 269842 (Camino_download_bug) Opened 20 years ago Closed 20 years ago

"Get Info" shows different file size for multiple downloads of same file

Categories

(Camino Graveyard :: Downloading, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: DekuDekuplex, Assigned: mikepinkerton)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041113 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041113 Camino/0.8+

When I downloaded Camino-0.7.dmg.gz using Camino from
http://ftp.mozilla.org/pub/mozilla.org/camino/releases/ and checked the file
size using "Get Info," I found different file sizes for multiple downloads of
the same file.  Although there was apparently no difference in functionality, it
was disturbing that some of the downloads seemed to differ in file size by about
ten bytes or so.

Reproducible: Sometimes
Steps to Reproduce:
1. Fire up Camino 0.8+ (build 2004111308).
2. Visit http://ftp.mozilla.org/pub/mozilla.org/camino/releases/ .
3. Click on "Camino-0.7.dmg.gz."
4. After downloading the file, check the file size using "Get Info."
5. Repeat steps 1 - 4 at least three times.
Actual Results:  
Occasionally, the file size differed by about ten bytes.

Expected Results:  
The file size should be exactly the same, no matter how many times I download
the same file.

System version: Mac OS X 10.2.6 (6L60) Jaguar
Kernel version: Darwin Kernel Version 6.6: Thu May  1 21:48:54 PDT 2003;
root:xnu/xnu-344.34.obj~1/RELEASE_PPC
Account: Administrator (admin)
Machine model: PowerBook5,1 (version = 3.3) (PowerBook G4 17-inch [Rev. A])
Machine speed: 1.0 GHz
RAM: 512 MB
HD: 55.88 GB (30.17 GB available)
Alias: Camino_download_bug
Severity: critical → normal
could be something to do with the mirrors, but trust me, it's not anything wrong
with camino.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.