[
https://issues.apache.org/jira/browse/CMIS-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348385#comment-14348385
]
Michael Brackx edited comment on CMIS-893 at 3/5/15 8:33 AM:
-------------------------------------------------------------
Yes, as it is better to be strict, an error would be good.
If you prefer not to be strict then a repositoryInfo response is more logical
than a repositoryInfos.
Some examples of things that could go wrong:
* using a repository url as the browser url
* an (incorrect) cmis client forgets the cmisselector and does an expensive
getRepositories call for each getRepositoryInfo
Being strict helps the CMIS ecosystem.
was (Author: brackxm):
Yes, as it is better to be strict, an error would be good.
If prefer not to be strict then a repositoryInfo response is more logical than
a repositoryInfos.
Some examples of things that could go wrong:
* using a repository url as the browser url
* an (incorrect) cmis client forgets the cmisselector and does an expensive
getRepositories call for each getRepositoryInfo
Being strict helps the CMIS ecosystem.
> getRepositories on browser binding repository url
> -------------------------------------------------
>
> Key: CMIS-893
> URL: https://issues.apache.org/jira/browse/CMIS-893
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.12.0
> Reporter: Michael Brackx
> Assignee: Florian Müller
>
> A http get on a repository url returns a getRepositories response.
> This can be confusing and have security implications.
> Example curl:
> {code}
> curl http://localhost:8080/browser/something
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
