Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | Issue #1656 - Part 6: Clean up the build files | Moonchild | 2020-09-23 | -1/+0 |
| | ||||
* | Issue #1656 - Part 3: Nuke more vim config lines in the tree. | Moonchild | 2020-09-23 | -5/+0 |
| | | | | Another S&R run with some smarter matching. | |||
* | Issue #80 - De-unify netwerk/protocol/ftp | Moonchild | 2020-05-18 | -1/+5 |
| | ||||
* | Fix whitespace. | athenian200 | 2020-01-26 | -1/+1 |
| | ||||
* | Issue #1349 - Stop 2xx FTP responses from causing browser to hang. | athenian200 | 2020-01-26 | -4/+20 |
| | | | | | | LIST and RETR still appear to work as intended on ftp:// URLs after my changes. I wasn't able to test STOR because the browser doesn't appear to support FTP uploads at this time (although our FTP implementation appears perfectly capable of doing an FTP upload.) If I understood the issue correctly, though, what we're doing is ensuring that we receive a preliminary 100 response from the FTP server for a given action before jumping to the 200 code describing what we do if the action was completed. Even though it makes no logical sense for a server to say an action was completed before it was initiated, someone could write a really annoying FTP server that takes advantage of this fact to crash the browser if they wanted. | |||
* | Convert UI-dictating FTP errors to console errors. | wolfbeast | 2019-03-23 | -118/+4 |
| | ||||
* | Remove MOZ_WIDGET_GONK [2/2] | wolfbeast | 2018-05-13 | -56/+0 |
| | | | | Tag #288 | |||
* | Bug 1351392 - Fix transport status events for http2 and ftp | janekptacijarabaci | 2018-02-11 | -0/+2 |
| | ||||
* | Add m-esr52 at 52.6.0 | Matt A. Tobin | 2018-02-02 | -0/+10334 |