I have a batch file that I wrote, which takes in several parameters. One of these key parameters is the remote upload path (utilized in the -p parameter). In one of my sites, I don't have a remote path (i.e, I want to upload the file exactly where I log in), however, if I pass "" as the parameter, it completely bombs out. Actually according to the log file, it tries to connect via a completely different interface. I wasn't sure what it was doing behind the scenes?!?!
However, if I put a "." as the parameter everything works fine. It took me quite some time to debug because the log file was telling me it was connecting to an internal IP address via port 21 and not the actual site or port that was configured in my CoreFTP gui.
Any clue?
Basic code:
set FTPExePath="C:\Program Files (x86)\coreftp\corecmd.exe"
set FTPProfile=%1
set FTPSource=%2
set FTPDest=%3
set FTPLog=%4
%FTPExePath% -s -O -u %FTPSource% -p %FTPDest% -site %FTPProfile% -log %FTPLog%
So again if I called ftpupload.bat with "" as the destination parameter it attempted to connect to an invalid host...but when I passed ".", everything worked great.