Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

200 Response codes over SSL/Proxy #2

Closed
campbellcharlie opened this issue Dec 14, 2014 · 3 comments
Closed

200 Response codes over SSL/Proxy #2

campbellcharlie opened this issue Dec 14, 2014 · 3 comments

Comments

@campbellcharlie
Copy link

If you use wfuzz 2.1 to scan an SSL host over a http proxy like burp suite, wfuzz will always report a 200 response code, this did not happen in 2.0. I would assume its getting the 200 SSL connect and reading that as the HTTP response code.

I tested the same settings over HTTP through the HTTP proxy and the response codes were correct.

PS. Very nice work! Glad to see wfuzz isn't dead.
@campbellcharlie
Copy link
Author

Found its not a wfuzz issue... more user related issue. Its working normally.

@campbellcharlie
Copy link
Author

Argh sorry for the spam, I thought it was due to having the proxy set to invisible mode but.. turns out its still reporting 200 response codes.

@xmendez
Copy link
Owner

xmendez commented Dec 16, 2014

Thank you for the feedback!

@JeffreyShran JeffreyShran mentioned this issue Jan 22, 2024
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xmendez @campbellcharlie