You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2008/04/08 18:21:24 UTC

[jira] Commented: (NET-205) Allow FTPFile entries to be generated even if date parsing fails

    [ https://issues.apache.org/jira/browse/NET-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586869#action_12586869 ] 

Sebb commented on NET-205:
--------------------------

Not entirely sure this is needed, given that the problem only occurs if the wrong parser is used.

However, assuming that it does make sense to protect against using the wrong parser, then perhaps this check - or something like it - should be applied to any of the other parsers?

> Allow FTPFile entries to be generated even if date parsing fails
> ----------------------------------------------------------------
>
>                 Key: NET-205
>                 URL: https://issues.apache.org/jira/browse/NET-205
>             Project: Commons Net
>          Issue Type: Improvement
>            Reporter: Sebb
>             Fix For: 1.5, 2.0
>
>         Attachments: AllowUnparseableDates.patch, net-205-invalidDates.diff.txt
>
>
> Most of the FTPEntryParser classes return null if date parsing fails.
> This can cause an otherwise good entry to be ignored, when perhaps the only problem is that the parsing is faulty.
> The suggestion is to allow such entries to be kept, but with a null date.
> This is already done by the EnterpriseUnixFTPEntryParser.
> Patches to follow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.