Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Wed, 12 Jun 2013 11:18:20 +0000 (UTC)
From: =?utf-8?Q?Florian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: <JIRA.12652371.1371033898374.103626.1371035900111@arcas>
In-Reply-To: <JIRA.12652371.1371033898374@arcas>
References: <JIRA.12652371.1371033898374@arcas>
Subject: [jira] [Commented] (CMIS-670) Query parameters kill browser cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CMIS-670?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D136811=
25#comment-13681125 ]=20

Florian M=C3=BCller commented on CMIS-670:
-------------------------------------

I don't see an issue here.
- The current behavior is not incompatible with the spec. It only construct=
s URLs that shouldn't be cached by clients. That's absolutely valid.
- The CMIS spec does not talk about caching. It doesn't define if a content=
 stream should be cacheable or not. In fact, some repositories intentionall=
y try to prevent caching on the client side. Different use cases have diffe=
rent caching requirements. There isn't one right way.
- The OpenCMIS server provides means to set an expiration time (-> "...unle=
ss the server provides an explicit expiration time"). So, there is a workar=
ound.
- The Browser binding has been designed to be accessed by web browsers. The=
 AtomPub binding has not.

I guess the improvement you are looking for is to change=20
http://server/content?id=3D1234-1234-1234-1234 to something like http://ser=
ver/content/1234-1234-1234-1234 .


               =20
> Query parameters kill browser cache
> -----------------------------------
>
>                 Key: CMIS-670
>                 URL: https://issues.apache.org/jira/browse/CMIS-670
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: opencmis-server
>    Affects Versions: OpenCMIS 0.9.0
>            Reporter: Carlo Sciolla
>            Priority: Critical
>
> From the [w2c spec|http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html=
#sec13.9]:
> {quote}
> We note one exception to this rule: since some applications have traditio=
nally used GETs and HEADs with query URLs (those containing a "?" in the re=
l_path part) to perform operations with significant side effects, caches MU=
ST NOT treat responses to such URIs as fresh unless the server provides an =
explicit expiration time. This specifically means that responses from HTTP/=
1.0 servers for such URIs SHOULD NOT be taken from a cache. See section 9.1=
.1 for related information.
> {quote}
> Currently, the getContentStream call in the REST binding requires URLs to=
 be in the form:
> http://server/content?id=3D1234-1234-1234-1234
> which is incompatible with the spec (e.g. Firefox won't cache such URLs)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira