[
https://issues.apache.org/jira/browse/NET-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501047
]
Rory Winston commented on NET-159:
----------------------------------
Hi guys
Thanks for the comments. I have analysed the issue, and here are my conclusions:
1. The synopsis you guys have given of the root cause of this issue is correct.
If the date fits the recent date format, and the server timestamp > local
timestamp, excluding any explicitly specified drift due to timezone
differentials, then this problem will occur.
2. FTPClient has no way of knowing when it is and when it is not correct to
roll back the date. The default bahviour is to always roll back.
I have added a method to FTPClient (setDateRollbackPermitted(boolean)). Call
this method with value of "false" to explicitly disallow this behaviour. This
should fix what you are seeing. I am marking this as fixed and doing a checkin.
If any of you guys would like to check out the source and try my patch, you are
most welcome.
As usual, any problems, let me know.
> FTPFile.getTimestamp() is off by one year
> -----------------------------------------
>
> Key: NET-159
> URL: https://issues.apache.org/jira/browse/NET-159
> Project: Commons Net
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: winxp, jdk 1.5
> Reporter: dangerOp
> Priority: Minor
> Fix For: 2.0
>
>
> The Calendar object returned by FTPFile.getTimestamp seems to be short by one
> year.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
