Fiddler Ideas

The free web debugging proxy for any browser, system or platform.

Improve debugging of malformed response headers.

Please see 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.

  • Eric Lawrence
  • Jan 18 2018
  • Under review
  • Attach files
  • Eric Lawrence commented
    18 Jan, 2018 06:06pm

    (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)