sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Rudolph (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (SLING-7357) Send Content-Type header along with the DistributionPackage's content in forward distribution
Date Sun, 07 Jan 2018 09:45:04 GMT

     [ 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)

Mime
View raw message