Sftp versus SOAP call to transfer files

I need to transfer some files to a third party. We can come up with a file format, but we want to keep it simple, for example, CSV. These will not be large files - only 10 with MB, and there will not be so many - 3 files per night.

Our priority for the protocol is sftp. We have done this in the past, and we understand it well.

Their preference is to do this through a call to the / SOAP / https web service.

The reasons they give are reliability, mainly because they got the whole file.

I do not buy this as a killer argument. You can easily create something during the file transfer process using sftp to make sure the transfer is complete, for example. use headers / footers in files or move files between directories, etc.

The only argument I can come up with is that through http (s) the ports 80/443 will be open, so there may be less firewalls for our infrastructure guys.

Can you imagine any other arguments in this regard? Is there a consensus on what would be best here?

Thanks in advance.

+3
source share
2 answers

File completeness is a common problem in "managed file transfer." If you compromised on “best practice,” you would end up working as AS / 2 (the web service is ish for transferring files including non-repudiation through signed integrity checks) or AS / 3 (the same thing via FTP or FTPS) .

SFTP , , FTP FTPS. , XSHA1 SFTP , .

, (, , ), - - ... .

, , , -, , , . ( jsut, , SOAP... - , .)

, /​​/ file-to-SOAP ( ), sftp-, .

+5

sftp - , soap - ( -), .

, sftp -

+1

All Articles