[
https://issues.apache.org/jira/browse/CONNECTORS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827151#comment-13827151
]
Karl Wright commented on CONNECTORS-814:
----------------------------------------
It seems that in other contexts, WGET simply appends ".<number>" to the file,
starting at 1, when there's a collision. I wonder if it does the same thing
here? The results would be
foo.com/next
foo.com/next.1/bar.html
... OR:
foo.com/next/bar.html
foo.com/next.1
No idea what it really does though, yet. I can't find a site that is set up in
a way that would demonstrate the issue.
> FileSystem output connector does not properly handle case where a path and a
> file collide
> -----------------------------------------------------------------------------------------
>
> Key: CONNECTORS-814
> URL: https://issues.apache.org/jira/browse/CONNECTORS-814
> Project: ManifoldCF
> Issue Type: Bug
> Components: File system connector
> Affects Versions: ManifoldCF 1.4.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.5
>
>
> Let's say the website defines a URL like this:
> http://mysite/news
> That URI actually gets mapped to a file on the web server, say
> http://mysite/news/index.html, but the http://mysite/news URI does exist and
> gets sent as the documentURI to addOrReplaceDocument().
> MCF's FileSystem connector gets the http://mysite/news URL and creates a
> directory for saving that content that looks like this http/mysite/news,
> where news is a file.
> But then if the site also defines a URL like this
> http://mysite/news/local/today.html, MCF's FileSystem connector fails trying
> to create the directory http/mysite/news/local because part of it,
> http/mysite/news, already exists as a file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
