The chunked content is corrupt. Chunk Length was malformed.

1 Answer 20 Views
Fiddler Classic
JAMES
Top achievements
Rank 1
JAMES asked on 22 Mar 2024, 09:17 PM
Trying to debug a chunked encoding response that looks correct to me. But when clicking on decode in response inspector I get the error "HTTP Error.. The chunked content is corrupt. Chunk Length was malformed. Offset 19". 
My question is, why does Fiddler think this is corrupt as the chunk lengths and encoding seems correct. And more specifically, how do I know what position "offset 19" is referring to so I can investigate further?

1 Answer, 1 is accepted

Sort by
0
Nick Iliev
Telerik team
answered on 25 Mar 2024, 07:38 AM

Hello James,

 

It can be difficult to determine the cause of the offset position error, as it could be caused by a variety of factors. For instance, it could be related to the 19th position in the chunked content, or the content itself may be corrupted. In such cases, the bytes could be shifted with 19 positions, and filled with trailing zeros. You can also send us the SAZ file that contains the session (which causes the error message) and/or the API endpoints (if these are public) that we can use to reproduce the issue.

It's possible that this issue could be related to the client's application response, which may be broken at the origin. One way to troubleshoot this would be to test the same request using Fiddler Everywhere and observe whether you receive the expected outcome or a more detailed error message.


 

Regards,
Nick Iliev
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Tags
Fiddler Classic
Asked by
JAMES
Top achievements
Rank 1
Answers by
Nick Iliev
Telerik team
Share this question
or