From oak-issues-return-63469-archive-asf-public=cust-asf.ponee.io@jackrabbit.apache.org Wed Jul 18 06:49:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7E8BF180636 for ; Wed, 18 Jul 2018 06:49:03 +0200 (CEST) Received: (qmail 80919 invoked by uid 500); 18 Jul 2018 04:49:02 -0000 Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-issues@jackrabbit.apache.org Received: (qmail 80907 invoked by uid 99); 18 Jul 2018 04:49:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2018 04:49:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 15B19C0910 for ; Wed, 18 Jul 2018 04:49:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ACoAN9noLniI for ; Wed, 18 Jul 2018 04:49:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E39B15F35B for ; Wed, 18 Jul 2018 04:49:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6DC35E00B5 for ; Wed, 18 Jul 2018 04:49:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 168B023F97 for ; Wed, 18 Jul 2018 04:49:00 +0000 (UTC) Date: Wed, 18 Jul 2018 04:49:00 +0000 (UTC) From: "Julian Reschke (JIRA)" To: oak-issues@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OAK-7637) [DirectBinaryAccess][DISCUSS] How to set response headers for direct download URIs? 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/OAK-7637?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D165473= 64#comment-16547364 ]=20 Julian Reschke commented on OAK-7637: ------------------------------------- {quote}I will add the ability to specify whether the content disposition sh= ould be "inline" or "attachment" as well as the filename.=C2=A0 (After disc= ussion Alex and I didn't think we need to support "filename*" for the conte= nt disposition; [~reschke] do you agree?) {quote} - who is in the position to decide what the disposition type is?=20 - I thought filename was added to make "save as" behave sanely? > [DirectBinaryAccess][DISCUSS] How to set response headers for direct down= load URIs? > -------------------------------------------------------------------------= ---------- > > Key: OAK-7637 > URL: https://issues.apache.org/jira/browse/OAK-7637 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-cloud, blob-cloud-azure > Reporter: Matt Ryan > Assignee: Matt Ryan > Priority: Major > > There are at least three headers that need to be set in responses to dire= ct GET URIs: > * {{Content-Type}} > * {{Content-Disposition}} > * {{Cache-Control}} > In order for the URIs to behave as expected when directly reading a binar= y, these headers should be set. > h3. Content-Type > Binary data is stored in an Oak repository as raw bytes only, with no ass= ociated content type.=C2=A0 When a client obtains a download URI and issues= a request to that URI, the resulting response should have the {{Content-Ty= pe}}=C2=A0header set so that the binary data will be interpreted properly b= y the client. > h3. Content-Disposition > Binary data is stored in an Oak repository using a system-generated ident= ifier for the blob, which is not a user-friendly name for the content being= represented.=C2=A0 When a client obtains a download URI and issues a reque= st to that URI, the resulting response should have the {{Content-Dispositio= n}} header set to a user-friendly name for that binary.=C2=A0 For example, = a PDF document stored in the repository as "TeamGoals.pdf" would have a com= pletely different blob name, and the generated URI to read that PDF directl= y from storage would also have that unhelpful name.=C2=A0 If the {{Content-= Disposition}} header is set, then an end user trying to save the PDF from a= web page link would save it using the name returned in the {{Content-Dispo= sition}} header rather than the blob name. > h3. Cache-Control > Since binary data in an Oak repository is essentially not changed after i= t is created, it is cacheable, so the {{Cache-Control}} header should be se= t to allow the binary to be cached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)