hiteksoftware.com

[cbidmea]

I have come across an issue while evaluating the JASFTP (8.0) product:

Running a simple task that connects to a Globalscape FTP server and retrieves files with the timestamp retained, since moving to BST the files are now out by 1 hour. Interestingly when connecting to an IIS FTP server the timestamp is correct.

Upon looking into this issue further it appear your software may be using the MDTM command which assumes that the FTP servers files have a time stamp of GMT. (http://kb.globalscape.com/article.aspx?id=10202&query=time) Can you let me know if there is a workaround for this issue. I.E. modifying the timestamp as part of the task or this this will require a code fix to the application to say set the Timezone of the FTP server we are connecting to.

[Robert]

which FTP module are you using? FTP-j or FTP?

[cbidmea]

Hi we are using the FTP-j module.

[Robert]

Try the FTP module. Do you get the same results using the FTP module?

[cbidmea]

HI, The FTP module seems to have other problems with Globalscape FTP server in that it will connect but you are unable to view files / folders or retrieve them via a task.

[Robert]

We will look into this issue.

Send us your support files using the help menu/ email support generator:
Task to Analyze - select your Ftp-j & Ftp task titles.
Click on ZIP button.
email us the support.zip file.

The reason we have 2 FTP/SFTP modules is to deal with buggy FTP servers. The chances that a FTP server has problems with 2 separate 3rd party FTP client api's should be low .

[cbidmea]

HI, All details have been sent acress JaSFtp Support Request. ID - 041820081430

[Robert]

We have verified that this is an issue with the GET maintain timestamp option in the FTP-j task. We will fix this in version 8.03 to be released next week. Thanks for reporting this.