summaryrefslogtreecommitdiffstats
path: root/config
diff options
context:
space:
mode:
authorathenian200 <athenian200@outlook.com>2020-01-26 01:40:55 -0600
committerathenian200 <athenian200@outlook.com>2020-01-26 01:40:55 -0600
commit8bb5db350d302f12aff7688a850ee51885e0e803 (patch)
treeba191c2aafdf7b33118b608d30276cf9e2ce038c /config
parenta64ac6d7022e4c88149d897864f857dce1063249 (diff)
downloadUXP-8bb5db350d302f12aff7688a850ee51885e0e803.tar
UXP-8bb5db350d302f12aff7688a850ee51885e0e803.tar.gz
UXP-8bb5db350d302f12aff7688a850ee51885e0e803.tar.lz
UXP-8bb5db350d302f12aff7688a850ee51885e0e803.tar.xz
UXP-8bb5db350d302f12aff7688a850ee51885e0e803.zip
Issue #1349 - Stop 2xx FTP responses from causing browser to hang.
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.
Diffstat (limited to 'config')
0 files changed, 0 insertions, 0 deletions