Chris's Wiki :: blog/web/FTPDeprecationAndSearching Commentshttps://utcc.utoronto.ca/~cks/space/blog/web/FTPDeprecationAndSearching?atomcommentsDWiki2020-12-07T05:34:40ZRecent comments in Chris's Wiki :: blog/web/FTPDeprecationAndSearching.By rwoodsmall on /blog/web/FTPDeprecationAndSearchingtag:CSpace:blog/web/FTPDeprecationAndSearching:951ddea9a6c1e1983364ea95063932b60a6e2cfbrwoodsmall<div class="wikitext"><p>Chrome has indeed disabled FTP support but it can still be enabled with a flag, at least on Chrome OS. This certainly won't last forever.</p>
<p>I don't believe any of these developments are good for anyone, and you're correct about the negative repercussions to findability as search and indexing are rooted out for insecure protocols, including non-S HTTP. I don't have an answer for this one, but ended up throwing together a little mod_proxy_ftp config like the below for Apache to at least be able to actually browse FTP links:</p>
<pre>
#
ProxyRequests On
ProxyPreserveHost On
RewriteEngine On
RewriteRule "^/ftp/(.*)$" "ftp://$1" [P]
#
</pre>
<p>Frankly I'm getting very, very tired of Google choosing what is best for everyone, and Mozilla quickly following suit with their us-too policy. The push toward a more secure internet is all well and good, but I'm a grown up. I know the risks with insecure FTP and HTTP and I'm willing to accept them. That's my choice, and the constant technological second guessing is getting old.</p>
</div>2020-12-07T05:34:40Z