On Jun 25, 2014, at 3:07 PM, Walsh, Peter <peter.wa...@disney.com> wrote:
> Hello, > I just upgraded from 4.2.1 to ATS 5.0.0 but am having issues in my plugins > that use TSHttpConnect. > > When the response body is chunked, the response body being returned to my > plugin includes the chunk sizes in the response string. In ATS 4.x, the > plugins received the response body without the chunked sizes as part of it, > meaning ATS handled this under the covers so my plugin didn't have to. > > Is that intentional behavior or a bug? I did not see it mentioned in the > release notes or with the output of the apichecker.pl tool TSHttpConnect has never dealt with chunked encoding automatically. The changes Kit and Bryan are referring to are in the TSFetchUrl API, which is entirely different. Has something changed in your environment, or are we now sending something different that causes the origin to respond differently? J
