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

This is an example of how this "standards body" really didn't represent the market place,  its users, its implementations.  It made a unreasonable decision to pull a still viable FTP protocol standard resource still used across the globe and at all scales.   

So now I have to see what this means, what browsers are using the same base code, which are following suit, whether it is deprecated or disabled or completely pulled, begin to inform customers about this change, go thru dozens of company support resource sites to change download links, moving all overhead and files to a HTTPS server, and also begin doing what I have never done before with Chrome -- begin recommending non-chrome browsers to customers.

I just wanted to put it on the "record."  Thanks for your feedback.

Hector Santos, CTO
Santronics Software, Inc.







-- 
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-513247109