[ 
https://issues.apache.org/jira/browse/IO-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501852#comment-16501852
 ] 

Gary Gregory edited comment on IO-559 at 6/5/18 2:22 PM:
---------------------------------------------------------

[~mdima]: I am not sure we are ready for a release. For example, 
{{org.apache.commons.io.FileSystem}} needs to be flushed out or delayed to the 
next release.

In the meantime, you can use a snapshot build from 
[https://repository.apache.org/content/repositories/snapshots/commons-io/commons-io/2.7-SNAPSHOT/]
 (I just pushed one.)


was (Author: garydgregory):
[~mdima]: I am not sure we are ready for a release. For example, 
{{org.apache.commons.io.FileSystem}} needs to be flushed out or delayed to the 
next release.

> FilenameUtils.normalize should verify hostname syntax in UNC path
> -----------------------------------------------------------------
>
>                 Key: IO-559
>                 URL: https://issues.apache.org/jira/browse/IO-559
>             Project: Commons IO
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 2.6
>            Reporter: Stefan Bodewig
>            Priority: Major
>             Fix For: 2.7
>
>
> {{FilenameUtils.normalize}} will accept broken file names as UNC path even if 
> their hostname part doesn't match the syntax of a proper hostname. Using 
> certain hostnames like "." this may lead to strange side effects.
> Most likely the best fix will be to make {{getPrefixLength}} verify the 
> hostname part of a suspected UNC path and return a value of {{NOT_FOUND}} if 
> it is not a valid hostname - much like it does for triple slashes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to