http to https redirector

While setting 'Require secure connection before login' to Yes does redirect HTTP to HTTPS it also disables normal FTP traffic. Only SFTP and 'FTP over TLS' work when setting this option to Yes. Ideal it would be 2 different settings, one for FTP and one for HTTP.

While setting 'Require secure connection before login' to Yes does redirect HTTP to HTTPS it also disables normal FTP traffic. Only SFTP and 'FTP over TLS' work when setting this option to Yes. Ideal it would be 2 different settings, one for FTP and one for HTTP.

Why would anyone want this?

Either you want security or not...

If you care about legacy FTP, use different domains, that way you maintain control over what is secure and what not. If the clients can chose freely, you should consider everything insecure.

FTP file sharing is one thing. HTTP(s) is another.

Please don't let your limited view on security block the fact that we live in a world that's moving from insecure to secure nature. Since we're not quite there yet then supporting both is a must.

Also if you have a HA scalabe MFT cluster where all FTP is tunneled through then you would see that some transfers are not needing to be SSL wrapping.

We have files that are public and not secure and we also have other files that are highly protected and secured where access to them is ALWAYS SSL wrapped.

Why would we want to manager several FTP servers when we can do it all in one?? My time is to precious to manage 8 servers when I can get away with 4