When you rewrite your applications to become secure (i.e. URL = "" the latest versions of the browsers will complain if you leave URLs with the scheme ftp:// - and they don't really support sftp: or ftps:. They throw a 'mixed content' error if a page which is served via SSL has URLs which are not secure and ftp is one of these. You would use mod_proxy_ftp if you want to replace the ftp: URLs with https URLs, yet allow the existing ftp server with all its logging and associated metrics to serve these requests. I know some of the people who watch this list know the nuances of some of the modules and perhaps there was something obvious to make the mod_proxy_ftp pass the client IPs to the ftp server backend so that is why I posted here. The counterargument is to say ftp is obsolete so just do the metrics from the access_log.