Closed
Bug 112175
Opened 23 years ago
Closed 23 years ago
no error if downloaded file can't be moved to its final location
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: colin, Assigned: neeti)
Details
Downloading a file via FTP, if you specify a location that you do NOT have write
access to, no error is displayed, and the downloaded file remains in your tmp
area with that funny name.
Expected behavior: if the downloaded file can't be moved or copied, then I'd
expect to see an error message.
This is with M0.9.6, but its not new.
OpenVMS is built like UNIX. I'm sure I could reproduce this problem on Linux.
Comment 1•23 years ago
|
||
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•23 years ago
|
||
Is 55690 really the same problem? I took a quick look and it seemed to be
talking about the fact that a temporary file is used. My problem is if the
temporary file can't be moved to the final destination then there is no error
message given.
Reporter | ||
Comment 3•23 years ago
|
||
I'm really not sure that this is a dup of bug 55690. Here's my reasoning.
The rename() in LocalFileUnix::MoveTo comes back with an error and we
return with whatever that error NSRESULT_FOR_ERRNO-translates into. That
status bubbles up several routines until we reach
nsDocumentOpenInfo::OnStopRequest. In this routine we drop the bad status
on the floor and blindly return with NS_OK.
http://lxr.mozilla.org/seamonkey/source/uriloader/base/nsURILoader.cpp#252
is where we call the listener's OnStopRequest and ignore the return status.
The next line of code we unconditionally return with NS_OK. Isn't this why
the rename failure never gets displayed to the user?
I'm unduping until someone convinces me otherwise.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
no, it's not a dupe of that bug, but i don't think this is unreported.
Assignee: waterson → neeti
Status: REOPENED → NEW
Component: XP Miscellany → Networking
QA Contact: brendan → benc
see also bug 105386
*** This bug has been marked as a duplicate of 27609 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•