You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey guys, I used the req. smuggler probes to solve all the new labs, including the tunnel probes it was very helpful, but looks like its not working w/ HTTP/2 CL.
The main HTTP/2 probe always issues as HTTP/2 TE, also in the "LAB: H2.CL request smuggling".
The Tunnel probe CL only do 4 requests and stop, i've tried to use it in many cases and it didn't work.
The Tunnel probe TE works perfectly.
So I ended up solving the CL lab as TE as well, it confused me. Also noticed that almost of them has multiple solutions (CL and TE). I will not detail here because it will give spoiler to some ppl.
This is not a problem for this case, because its solvable as TE, but apparently it is really not detecting H2.CL in any way.
..btw, thank you for this amazing extension.
The text was updated successfully, but these errors were encountered:
Thanks for the heads up about the multiple solutions, we'll definitely make sure that doesn't happen in any H/2 related exam questions :)
Yeah I had some code to detect H2.CL but it caused too many false positives, and as H2.CL is really rare I left it out. We've included a lab on that primarily because it's good from a learning perspective. I'll leave this ticket open in case a good detection method turns up.
Hey guys, I used the req. smuggler probes to solve all the new labs, including the tunnel probes it was very helpful, but looks like its not working w/ HTTP/2 CL.
So I ended up solving the CL lab as TE as well, it confused me. Also noticed that almost of them has multiple solutions (CL and TE). I will not detail here because it will give spoiler to some ppl.
This is not a problem for this case, because its solvable as TE, but apparently it is really not detecting H2.CL in any way.
..btw, thank you for this amazing extension.
The text was updated successfully, but these errors were encountered: