You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2014/04/17 10:54:49 UTC
[jira] [Updated] (ACE-437) DeploymentServlet should never set
Content-Length
[ https://issues.apache.org/jira/browse/ACE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans updated ACE-437:
---------------------------------
Fix Version/s: next
> DeploymentServlet should never set Content-Length
> -------------------------------------------------
>
> Key: ACE-437
> URL: https://issues.apache.org/jira/browse/ACE-437
> Project: ACE
> Issue Type: Bug
> Components: Deployment
> Reporter: J.W. Janssen
> Assignee: Marcel Offermans
> Fix For: next
>
>
> ACE-435 stated that the DeploymentServlet did not always send a Content-Length header. After some discussion, we came to the conclusion that the effort we need to go through to determine the Content-Length in all situations is beyond reasonable with regards to the performance.
> Therefore, we need to remove the fix made for ACE-435 and ensure that the Content-Length is no longer send for deployment packages. We deliberately deviate from the HTTP-spec (RFC 2616) a bit, but this is acceptable in this situation as we're not providing a general purpose implementation anyway...
--
This message was sent by Atlassian JIRA
(v6.2#6252)