Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Double CRLF added on HTTP2 requests when adding through Burp API

Rafal | Last updated: Nov 16, 2021 12:48PM UTC

I have a curious bug with using Burp API in extensions - particularly when creating custom issues using "Add & Track Custom Issues" extension. When I create the issue - and copy & paste the response starting with HTTP/2, the corresponding request gets truncated after the first line. When reviewing it, it seems that there is double CRLF character after the HTTP protocol so rest of the headers is truncated. I verified it is not happening until Issue objects are created and this is only observable on HTTP/2 protocol requests and ONLY when copy pasting - when right clicking on the request and adding it as the issue I interestingly did not observe the issue. Also no issue when handling HTTP/1.1 in any way, so I reckon it has to be something with the handling of HTTP2 requests. I have a case where I need this functionality to work properly so would be grateful if you could look into it.

Hannah, PortSwigger Agent | Last updated: Nov 16, 2021 01:04PM UTC