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

using Connection: close instead of zero

[ | Last updated: Feb 25, 2022 09:33AM UTC

in this request : POST / HTTP/1.1 Host: vulnerable-website.com Content-Length: 3 Transfer-Encoding: chunked 8 SMUGGLED 0 tutorial(TE.CL vulnerabilities) says : The front-end server processes the Transfer-Encoding header, and so treats the message body as using chunked encoding. It processes the first chunk, which is stated to be 8 bytes long, up to the start of the line following SMUGGLED. It processes the second chunk, which is stated to be zero length, and so is treated as terminating the request. This request is forwarded on to the back-end server. I have a question about it: tutorial says zero(the second chunk) is treated as terminating the request. I want to know can we use instead of zero this --> Connection: close to say the front end connection is closed?

Liam, PortSwigger Agent | Last updated: Feb 28, 2022 08:35AM UTC