FTP is arguably a lot better for uploads as well as network devices don't make the same assumptions about length of connections etc with FTP that they do with HTTP.
David Connors [email protected] | M +61 417 189 363 Download my v-card: https://www.codify.com/cards/davidconnors Follow me on Twitter: https://www.twitter.com/davidconnors Connect with me on LinkedIn: http://au.linkedin.com/in/davidjohnconnors On Fri, Oct 18, 2013 at 1:22 PM, Grant Maw <[email protected]> wrote: > Just a side-comment - maybe we're luddites here, but we use FTP all the > time to get things from A to B. Every single day. I know it's old, but it's > still useful. > > > On 18 October 2013 09:46, Greg Keogh <[email protected]> wrote: > >> >You do need a higher end firewall though. >>> >> >> I didn't want to confuse matters previously, but now things have calmed >> down I can add that the offending server is actually inside an Amazon AWS >> server instance. I turned off the Windows firewall ages ago, but Amazon >> have their own "Security Group" feature where you say which >> inbound/outbound ports are open. I'm not sure why they have such a "meta >> firewall" as it just confuses things for customers. It turns out that this >> feature was irrelevant to our problem anyway. >> >> The other good news is that the chap writing the Borland C++ code found a >> passive switch which lets his ftp operations work perfectly. I'm still >> going to urge him over to http instead. >> >> Greg K >> > >
