You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Struberg (JIRA)" <ji...@codehaus.org> on 2011/05/27 00:25:22 UTC
[jira] Closed: (WAGON-332) Treat STAT return code 200 (command ok)
as valid result
[ http://jira.codehaus.org/browse/WAGON-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg closed WAGON-332.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0
> Treat STAT return code 200 (command ok) as valid result
> -------------------------------------------------------
>
> Key: WAGON-332
> URL: http://jira.codehaus.org/browse/WAGON-332
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ftp
> Affects Versions: 2.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 2.0
>
>
> we currently only check 213 (file exists) 150 (file status ok) and 211 (system ok).
> FTC-959 ( http://www.faqs.org/rfcs/rfc959.html ) defines the following return values for STAT:
> STAT
> 211, 212, 213
> 450
> 500, 501, 502, 421, 530
> This doesnt contain the 200 value, but command ok is defined as being returned in case the server doesnt have more info to pass. This happened with a fairly recent ftp server. I'm also curious why we dont detect 212 but intead use 150 as ok indicator.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira