If I understand your question, mod_proxy_ftp does not speak ftp to the
client; only between the httpd server and backend. So the only data channel
is the one established by httpd to shuttle the data.
On Tue, Jul 24, 2018, 12:28 Harbo, Peter wrote:
> The mod_proxy_ftp module is working fine for
When you rewrite your applications to become secure (i.e. URL = 'https'),
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 a
On 24.07.2018 19:28, Harbo, Peter wrote:
The mod_proxy_ftp module is working fine for me using release 2.4.25
to send urls matching a pattern to a proftpd server running on the
same system. I have noticed that the source IP address in the ftpd
log is the same as the httpd running the mod_proxy
