On 2017 Feb 12 19:27:28, you wrote to me:

 ml>> you can't http to ftp anyway... there has to be a http server
 ml>> there... you can ftp to it, though...

 EK> If I change my wildcat ftp port to 2121 I can web browse
 EK> wildcats file areas with no problem. It generates an
 EK> index file with file descriptions. Must be Wildcat
 EK> specific ftp feature.

yes... wildcat is apparently listening on the ports and generating the
proper traffic for the connections and their protocols that it receives...
generally speaking, though, with a browser, you put in the protocol to
use... if you are going to a web site, you use http or https... if you are
going to a ftp site, you use ftp or, if your browser and the destination
server support it, ftps...

eg:
  http://some.site.foo
   ftp://some.site.foo

the critical part, beside having the address correct, is the protocol
leader on the left of the "://" delimiter...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'
it wrong...
... An expert is someone from out of town with a briefcase.
---