[jira] [Resolved] (TS-1643) Traffic Server 3.2.0 sends default error response instead of "request#no_content_length" for Post requests with no Content-Length header.

["James Peach (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Peach resolved TS-1643.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 3.3.1
         Assignee: James Peach

4a614a967f60eaad8fa2771de7261a4da35a10df TS-1643: Post requests with no Content-Length header sends default error response

thanks!
                
> Traffic Server 3.2.0 sends default error response instead of "request#no_content_length" for Post requests with no Content-Length header.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TS-1643
>                 URL: https://issues.apache.org/jira/browse/TS-1643
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: Mudassar Jafer
>            Assignee: James Peach
>             Fix For: 3.3.1
>
>
> When custom error responses are enabled and HTTP post request is sent with no "Content-Length" header Traffic server sends back the default response instead of "request#no_content_length".
> To reproduce the issue following records.config configuration variable should be set to 1.
> proxy.config.body_factory.enable_customizations
> In function "HttpTransact::is_request_valid" the following function call is not correct.
> build_error_response(s, HTTP_STATUS_BAD_REQUEST, "request#no_content_length", "Content Length Required", const_cast < char *>(URL_MSG));
> The third and fourth parameters should be swapped.
> build_error_response(s, HTTP_STATUS_BAD_REQUEST, "Content Length Required", "request#no_content_length", const_cast < char *>(URL_MSG));

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