Return-Path: X-Original-To: apmail-chemistry-dev-archive@www.apache.org Delivered-To: apmail-chemistry-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 16C0C10417 for ; Thu, 5 Mar 2015 08:33:39 +0000 (UTC) Received: (qmail 25455 invoked by uid 500); 5 Mar 2015 08:33:38 -0000 Delivered-To: apmail-chemistry-dev-archive@chemistry.apache.org Received: (qmail 25413 invoked by uid 500); 5 Mar 2015 08:33:38 -0000 Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@chemistry.apache.org Delivered-To: mailing list dev@chemistry.apache.org Received: (qmail 25274 invoked by uid 99); 5 Mar 2015 08:33:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Mar 2015 08:33:38 +0000 Date: Thu, 5 Mar 2015 08:33:38 +0000 (UTC) From: "Michael Brackx (JIRA)" To: dev@chemistry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CMIS-893) getRepositories on browser binding repository url MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CMIS-893?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D143483= 85#comment-14348385 ]=20 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 logic= al 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 t= han 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=C3=BCller > > 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)