[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mina-dev
Subject:    [jira] Resolved: (FTPSERVER-345) Update the replies of MD5 and MMD5
From:       "Sai Pullabhotla (JIRA)" <jira () apache ! org>
Date:       2010-01-28 13:39:35
Message-ID: 1553018845.105301264685975047.JavaMail.jira () brutus ! apache ! org
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/FTPSERVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Sai Pullabhotla resolved FTPSERVER-345.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.0

Committed the fix to trunk and 1.0.x branch. 

> Update the replies of MD5 and MMD5 commands to include the file path in double \
>                 quotes when there are spaces in the path
> -----------------------------------------------------------------------------------------------------------------------
>  
> Key: FTPSERVER-345
> URL: https://issues.apache.org/jira/browse/FTPSERVER-345
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.3
> Reporter: Sai Pullabhotla
> Priority: Minor
> Fix For: 1.0.4, 1.1.0
> 
> 
> Even though the RFC does not explicitly say this, the example replies showed in the \
> RFC enclose all file paths in double quotes. I'm not sure if there are any FTP \
> clients that look for double quotes presence. A smart FTP client could always grab \
> the checksum from the last token in the reply, where each token is separated by one \
> or more white spaces. In order to offer best compatibility, I would recommend \
> enclosing the file paths in double quotes when they contain any spaces. 

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


[prev in list] [next in list] [prev in thread] [next in thread]