Closed
Bug 418571
Opened 17 years ago
Closed 17 years ago
Data corruption: source file local copy truncated to zero length.
Categories
(Toolkit :: Downloads API, defect)
Toolkit
Downloads API
Tracking
()
VERIFIED
DUPLICATE
of bug 336900
People
(Reporter: greatnessguru, Unassigned)
References
()
Details
(Keywords: dataloss)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.12) Gecko/20080201 SeaMonkey/1.1.8
Build Identifier: All?
See Bug 336900.
That bug addresses the server mis-configuration issue.
This bug addresses the source file local copy
corruption issue (wrongfully truncated to zero length)
whenever the server is mis-configured as in Bug 336900.
Gecko/Firefox should not be fooled into
wrongfully corrupting the source file local copy
(by truncating it to zero length, or otherwise)
whenever the server is mis-configured
as in Bug 336900.
This happens whether one is trying to "Save to Disk"
or view/render the source file local copy on screen.
Thank you,
Eddie Maddox
Reproducible: Always
Steps to Reproduce:
Please see Bug 336900.
Actual Results:
Source file local copy is
wrongfully truncated to zero length.
Expected Results:
Source file local copy
should remain intact,
even when the source file server
is mis-configured.
Gecko/Firefox should have a Robust System for doing
"the right thing" with source file local copies
even when the source file server is mis-configured
and that mis-configuration is detectable.
See Bug 336900, please.
This is analagous to Gecko rendering
"the right thing" even when a website is mis-coded.
Gecko 1.9/Firefox 3 implements "reflow",
and/or other strategies,
to properly render websites even when
website source code is improperly written.
Gecko/Firefox should also implement strategies
to not corrupt source file local copies
(by truncating them to zero length, or otherwise)
even when source file servers are
improperly configured, such as in Bug 336900.
This can be the "tracking bug" for that effort.
Severity: Critical,
because corrupting the source file local copy
(by truncating it to zero length wrongfully)
"causes you to lose data".
In fact, after the wrongful truncation,
no data whatsoever remains. "Zero".
Thank you,
Eddie Maddox
Reporter | ||
Updated•17 years ago
|
Flags: blocking-firefox3?
Comment 1•17 years ago
|
||
Safari 3.0.4 also writes it on-disk as "0 bytes of ?".
Comment 2•17 years ago
|
||
(In reply to comment #1)
> Safari 3.0.4 also writes it on-disk as "0 bytes of ?".
But, interestingly enough, Opera 9.25 on Mac OS X 10.4 gets it right, it seems; I'll confirm this bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
![]() |
||
Comment 3•17 years ago
|
||
Uh... This is just a duplicate of bug 336900. We fail to get any data from the networking library, so there is no data to write.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Updated•17 years ago
|
Flags: blocking-firefox3?
Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•