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
Please tell me if there are any standards for the design strategy of the cases and what is the reason for still reporting "OK" despite the response code being 200
#34
Open
sunnie-star opened this issue
Jan 14, 2025
· 0 comments
Thank you very much for your work. I have two questions that I would like to ask you. Could you please answer them? Thank you very much!
Q1: Different agents may have different strategies for parsing headers and handling TE CL. How to design cases that are not too aggressive, but can truly intercept the risk of smuggling vulnerabilities
Q2: When I was testing the HTTP smuggling vulnerability interception function of my web server, when the response code was 200, there was no potential risk of displaying tecl or clte by this tool. However, if the interception was successful, it should be a response of 400 bad request. Could you please explain why the tool only displays tecl or clte risk when timeout according to your code?
Thank you very much again!
The text was updated successfully, but these errors were encountered:
Thank you very much for your work. I have two questions that I would like to ask you. Could you please answer them? Thank you very much!
Q1: Different agents may have different strategies for parsing headers and handling TE CL. How to design cases that are not too aggressive, but can truly intercept the risk of smuggling vulnerabilities
Q2: When I was testing the HTTP smuggling vulnerability interception function of my web server, when the response code was 200, there was no potential risk of displaying tecl or clte by this tool. However, if the interception was successful, it should be a response of 400 bad request. Could you please explain why the tool only displays tecl or clte risk when timeout according to your code?
![image](https://private-user-images.githubusercontent.com/54070096/402853174-2a6732d9-185f-45d7-80cf-c24b85b98aa3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5NzA5ODEsIm5iZiI6MTczODk3MDY4MSwicGF0aCI6Ii81NDA3MDA5Ni80MDI4NTMxNzQtMmE2NzMyZDktMTg1Zi00NWQ3LTgwY2YtYzI0Yjg1Yjk4YWEzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDIzMjQ0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWEwMzkyODQ3NDZkNmRiMDlhM2Y4Y2FlYjgyMDc2NmMyZDM5MDVlNTQ1MDZjYzJlODZiYzVmNDM1NDI0MGJjYWEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.6UyeMKthvvGPkYSYnVOtbLIAQHOFQ6JnUwFl2Z2EMcM)
Thank you very much again!
The text was updated successfully, but these errors were encountered: