Improve debugging of malformed response headers.

Progress® Telerik® Fiddler™ Classic Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Under Review

Last Updated: 18 Jan 2018 19:50 by Eric

Eric

Created on: 18 Jan 2018 05:59

Type: Feature Request

Improve debugging of malformed response headers.

Please see https://twitter.com/ericlaw/status/953987196654104576 for a summary of the problem and the current annoying workaround.

There used to be a TODO in the !bReadResponseOk block explaining how we needed to peek at the unprocessed data from the ServerPipe to see what bytes we /did/ get back.

1 comment

Eric

Posted on: 18 Jan 2018 06:00

(Further analysis of the scenario here is that the headers aren't malformed, but they're sent and the server chases them with a RST that causes the socket read to throw an exception. We still have 257 bytes of data though, and could show that to the user)