Closed
Bug 782085
Opened 12 years ago
Closed 9 years ago
Need event and progress notifications for FTP
Categories
(Core Graveyard :: Networking: FTP, defect)
Core Graveyard
Networking: FTP
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jduell.mcbugs, Unassigned)
References
Details
We need to add an "ftp-on-modify-request" nsIObserverService notification to FTP so we can block the connection if we need to for various policy reasons (see bug 780087). Presumably we can copy the logic from the HTTP version of the code.
Reporter | ||
Comment 1•12 years ago
|
||
We probably also want ftp-on-examine-response and ftp-on-examine-cached-response, like HTTP has.
We're also going to need a way to monitor how much traffic an FTP connection is using. That's probably a matter of implementing an nsIHttpActivityObserver and/or nsIProgressEventSink API for ftp, like we have for HTTP.
Comment 2•11 years ago
|
||
given the essentially deprecated status of ftp, I'd like to keep this to the absolute minimum set necessary. Maybe ftp-on-modify request would be enough?
Comment 3•9 years ago
|
||
We are in a period where ftp is clearly deprecated and in general, making changes to the code is riskier than letting it ride unless there is a patch and reviewer available to make a good judgment about it. So I'm going to wontfix ftp bugs related to enhancements, interop errors, etc.. We will be better off putting our energy into including a different js based ftp stack.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•8 months ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•