[
https://issues.apache.org/jira/browse/TS-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Syeda Persia Aziz updated TS-4819:
----------------------------------
Description: I found this when using the python "requests" library to
generate HTTP requests to test the ATS. The request method of this library
generates incorrect message body (i.e., does not follow the standard format) if
both Content-Length and chunked encoding are specified. ATS can handle requests
with these two fields being specified. It is the wrong format of the chunk that
makes the ATS crash. The test program to reproduce the issue is attached. If
the Content-Length is removed from the header, then the library generates the
correct format and ATS responds correctly. Ideally, content-length and chunked
encoding should not be specified together (was: I found this when using the
python "requests" library to generate HTTP requests to test the ATS. The
request method of this library generates incorrect message body (i.e. does not
follow the standard format) if both Content-Length and chunked encoding are
specified. ATS can handle requests with these two fields being specified. It is
the wrong format of the chunk that makes the ATS crash. The test program to
reproduce the issue is attached. If the Content-Length is removed from the
header, then the library generates the correct format and ATS responds
correctly. Ideally, content-length and chunked encoding should not be specified
together)
> ATS-6.2.x crashes if the message-body of a chunk is not correctly formatted
> ---------------------------------------------------------------------------
>
> Key: TS-4819
> URL: https://issues.apache.org/jira/browse/TS-4819
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Syeda Persia Aziz
> Attachments: test_post.py
>
>
> I found this when using the python "requests" library to generate HTTP
> requests to test the ATS. The request method of this library generates
> incorrect message body (i.e., does not follow the standard format) if both
> Content-Length and chunked encoding are specified. ATS can handle requests
> with these two fields being specified. It is the wrong format of the chunk
> that makes the ATS crash. The test program to reproduce the issue is
> attached. If the Content-Length is removed from the header, then the library
> generates the correct format and ATS responds correctly. Ideally,
> content-length and chunked encoding should not be specified together
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
