search

sleeyax / burp-awesome-tls

Burp extension to evade TLS fingerprinting. Bypass WAF, spoof any browser.
GNU General Public License v3.0
991 stars 66 forks source link

Requests being forced to use HTTP/1.1 protocol #73

Closed AmmeySaini closed 1 month ago

AmmeySaini commented 1 month ago

I did notice a weird behavior whenever I load the extension all of the requests go through the HTTP/1.1 protocol. I've confirmed and checked this without the extension and the requests are on HTTP2

without extension: image

with extension: image

sleeyax commented 1 month ago

This is a limitation regarding the way Awesome TLS works (see REAME.md#how-it-works). If you check the response from https://tls.peet.ws/api/all you can see it didn't actually send a HTTP 1 request, but a HTTP 2 request. It only looks that way in burp's request viewer because the server part(the "spoof TLS proxy" component as you can see on the diagram in the README) only supports HTTP 1. So it's more of a visual thing rather than an actual bug.

That being said, it's unfortunate that the used protocol information is lost. Maybe there's a way to improve this.

AmmeySaini commented 1 month ago

This is just for confirmation!!! so what you are saying is that no request is going through HTTP1, it's just there for the request viewer?? There's a thing that I'm currently working on, the requests work fine on HTTP1, but I'm somehow being profiled while using HTTP2, so I just need to make sure that the requests are actually going through HTTP2 even if they show HTTP1 in the Burp

sleeyax commented 1 month ago

so what you are saying is that no request is going through HTTP1, it's just there for the request viewer??

Correct.

There's currently no convenient way to confirm that HTTP 2 is used though, hence the new issue i created. I'll happily accept a PR for it if you're willing to give it a shot :)

AmmeySaini commented 1 month ago

I'll look into it. Thanks for the confirmation.