Closed Bug 459528 Opened 17 years ago Closed 15 years ago

nsIWebBrowserPersist incorrectly reports success when attempting to persist to an FTP folder which does not exist

Categories

(Firefox :: Extension Compatibility, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: david.rickard, Unassigned)

Details

(Whiteboard: [CLOSEME 2010-11-15])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 (.NET CLR 3.5.30729) When attempting to persist to a non-existent FTP folder, success is reported, when it should report failure. Reproducible: Always Steps to Reproduce: 1. Set up a nsIWebBrowserPersist object and tell it to persist an item to an ftp:// url. The server and login should be correct, but enter a non-existent folder to persist to. 2. Attach a nsIWebProgressListener. 3. Execute the persist and look in the onStateChange function. Check the aStatus variable when aStateFlags contains STATE_STOP. Actual Results: Result is reported as NS_OK. Expected Results: An error should be reported instead, because the persist failed.
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO. Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME. This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.