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

Why not also pull HTTP? 

That should not be your decision.  Just consider that not everything needs to be secured. Not everything needs to be encrypted with high overhead processing.  It should be left to the implementations and their operations.  There are public and private environments.  Don't assume everything is public and cloud-based.   There are many reasons why people would use a FTP resource.  There are private systems that have operated and still operate just fine for a long time, until now.   

The fact is, there is an extreme amount of overhead with just allowing for HTTPS especially today with enhanced ciphers encrypted packets going through DPI (Deep Packet Inspection), couple this with connectivity movement towards broadband, the overhead and network latency is far worst with higher delays, timeouts, resets, etc.    In my technical opinion, this will soon be a major problem.

Chrome's future needs to be better managed.  These poor decisions puts pressure for Chrome derivatives that do not follow highly subjective, to me,  market inexperienced,  main branch design change decisions.  To use a "low traffic" decision to pull FTP, imo, this was not a legit and reasonable reason. 

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