joknoxy

I can see another practical use-case here - if the server has added a WAF mitigation that looks for signs of **non-legitimate** request bodies and blocking those, then this feature...

I was puzzled too however worked it out. Wireshark decodes RFC-compliant HTTP requests as Protocol:HTTP and shows the HTTP request (or response) line 1 in the 'Info' column in Packet...