Re: [whatwg/fetch] Block 'ftp:' requests from non-'ftp:' clients. (#464)

I don't get this decision.  What makes it your right to decide what a private or public client/server system uses?  That's not "open" programming.  FTP is still a variable protocol used at all scales.  Sure, perhaps for legacy operations, but what isn't legacy today?   Even a browser is a legacy UI and HTTP method download is legacy!   Normally, in lieu of some security reason,  you would make this optional for end-users to decide.   Just because you measured "low traffic," (you didn't measure mine), in my design opinion, you don't take features out and break web access and backend operations to switch their load/storage resources.  geez





-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/464#issuecomment-512663981