Access Arabic-named files through FTP - ftp

I have a website hosted on GoDaddy windows servers. I want to move the website to another server. I tried to download the whole website files via FTP but there are some files which named in Arabic and when my FTP client (FireFTP) tries to save them on my pc, the file name becomes underscores (e.g. _______.jpg). I cannot change the file names because they are linked from the database (the website is a DotNetNuke CMS).
I am wondering if this problem is due to the FTP server itself or the FTP client I'm using?

I finally could solve this by writing a script (in ASP.NET/C#) to rename all files to numbers (e.g. 1.jpg, 2.doc ....) and then download the renamed files though FTP. The script also genrates commands to rename the files back to the original names in Arabic.

Related

Laravel app just on remote PC that accepts .zip and executes commands contained in .txt file. Results returned to client

I've been asked to set up a laravel app that, when running on a remote desktop, will accept two files via api: a .txt file and a .zip file. The text file would contain cmd prompt commands (e.g. 'ls'). The aim is then for the app to process the contents of the .zip file using the instructions in the .txt file and then return the result to the client (e.g. perhaps another text file with a list of the files in the zip file).
Struggling to know how best to approach it. I know the question is very vague (it's all I have) but very much appreciate any suggestions.

Using IIB File nodes to move, copy, download and rename (S)FTP files without opening them

I am using IIB, and several of the requirements I have are for message flows that can do the following things:
Download a file from an FTP and/or SFTP server to the local file system, with a different name
Rename a file on the local file system
Move and rename a file on the (S)FTP server
Upload a file from the file system to the (S)FTP server, with a different name
Looking at the nodes available (FileInputNode, FileReadNode, FileOutputNode); it appears that they can read and write files in this way; but only by copying them into memory and then physically rewriting the files - rather than just using a copy/move/download-type command, which would never need to open the file in the same way.
I've noticed that there's options to move store files locally once the read is complete, however; so perhaps there's a way around it using that functionality? I don't need to open the files into memory at all - I don't care what's in the files.
Currently I am doing this using a Java Compute Node and Apache Commons Net classes for FTP - but they don't work for SFTP and the workaround seems too complex; so I was wondering if there was a pure IIB way to do it.
There is no native way to do this, but it can be done using Apache Commons VFS

Access DBF from FTP Server

I Have a application on Clipper,DBF.
Is It Possible to access DBF file from FTP Server Using Clipper Program?
Thanks.
No, not really.
FTP is not a "shared folder". You can create a batch file which will download file via FTP, then run your clipper application, then after application finishes copy modified .DBF back to FTP server.
Note however that it will be slow (as you need to transfer whole .DBF file even if you need just a tiny bit of it) and that you MAY NOT use it at more than one place at a time (running it in more than one place will overwrite data, including possibility of file truncation/corruption)
There are utilities that present FTP as a filesystem ("shared folder"), for example curlftpfs, but while it allows you to just run .exe directly instead of via aforementioned .bat file, ALL THE LIMITATIONS mentioned in previous paragraph still apply - it is not possible to avoid them due to nature of FTP.

Windows: How to lock an FTP downloaded file

I have one application in which I download files from FTP server.
As the file is downloading, a third party begins uploading that file and so it ends up with a corrupt file and is unable to process it.
Does any know about how to deal with situation other than using .complete file mechanism? (keeping track of when the download is complete)
Is it possible to lock the file on the FTP server? The FTP server is windows.
No, there is no standard locking mechanism, it's all between up to you and the other party. Here are some ways to do it in addition to creating a .complete file;
The uploader uploads the file as file.xls.tmp, and when it's complete, rename to file.xls.
The uploader uploads to a tmp directory, and when it's complete, moves it to the scanned dir.
The uploader uploads the file, and the downloader scans file dates to find files written before a certain time. This is not as reliable, since a file from a crashed uploader may be scanned.
There are probably more versions, particularly with a custom ftp server, but using the plain standard doesn't allow for much "fancy stuff".

Dreamweaver and Binary PUT via FTP

As we all know (don't we?), the FTP functionality on Dreamweaver is inexcusable for a professional product, but I bear with it because Dreamweaver has other useful stuff that overshadows the FTP.
However, I have a specific FTP situation which has been annoying me for a few years now, and was hoping someone had a solution.
We use the ZEND encryption on some PHP files. Once you do that, the files are no longer text file (but instead, binary files).
My understanding is that Dreamweaver FTPs everything as binary (maybe I misunderstand?), but each time I upload (FTP) those ZEND-encrypted PHP files to a server using Dreamweaver, they do not work (just a white screen -- meaning they are corrupt).
I have to drop into the command-line FTP, FTP into the server, and manually PUT the files (after typing BIN of course). Not too hard, but adds extra steps I would rather avoid.
Is there any adjustment, tool, add-on, or ANYTHING that will force Dreamweaver to upload the files correctly?
Looks like you have to modify your FTPExtensionMap.txt, that's what Dreamweaver uses to select the FTP transfer mode.
Although that would make all .php files to be transferred in BINARY, which may not be what you want if you're transferring back & forth between Win/UNIX/Mac other non-encoded .php files
Here the instructions on how to modify the file.

Resources