From dev-return-85036-archive-asf-public=cust-asf.ponee.io@sling.apache.org Sun Jan 7 10:45:14 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id D1945180718 for ; Sun, 7 Jan 2018 10:45:14 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BD951160C17; Sun, 7 Jan 2018 09:45:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 172F0160C29 for ; Sun, 7 Jan 2018 10:45:13 +0100 (CET) Received: (qmail 73400 invoked by uid 500); 7 Jan 2018 09:45:12 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 73386 invoked by uid 99); 7 Jan 2018 09:45:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Jan 2018 09:45:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6B866C3C8C for ; Sun, 7 Jan 2018 09:45:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id GoEKkLZqgYvB for ; Sun, 7 Jan 2018 09:45:10 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2296F5FACE for ; Sun, 7 Jan 2018 09:45:10 +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 399D1E04C7 for ; Sun, 7 Jan 2018 09:45:07 +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 AC5ED240DE for ; Sun, 7 Jan 2018 09:45:04 +0000 (UTC) Date: Sun, 7 Jan 2018 09:45:04 +0000 (UTC) From: "Dirk Rudolph (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (SLING-7357) Send Content-Type header along with the DistributionPackage's content in forward distribution MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SLING-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dirk Rudolph updated SLING-7357: -------------------------------- Comment: was deleted (was: As sling requires java 8 the API change can be done with a default implementation for the content type returning application/octet-stream.) > Send Content-Type header along with the DistributionPackage's content in forward distribution > --------------------------------------------------------------------------------------------- > > Key: SLING-7357 > URL: https://issues.apache.org/jira/browse/SLING-7357 > Project: Sling > Issue Type: Improvement > Components: Content Distribution > Reporter: Dirk Rudolph > > Currently SimpleHttpDistributionTransport only adds Connection and Digest http header (if configured to do so) to the http request. When integrating into other systems then sling the API might require the content type of the package transmitted to be present. > I see to options to support that: > a) implement configureable headers for the http transport similar to the timeouts. This might clash with headers set by the implementation > b) let the serializer specify the type of the content it generates. This will be an API change in the core bundle. > From my perspective b) will be simpler to implement. -- This message was sent by Atlassian JIRA (v6.4.14#64029)