Replies: 2 comments
-
|
Yes, pipe katana output into httpx and use # Match by common login keywords in the response body
katana -u https://target.com -silent | httpx -mr "(?i)(type=.?password|login|sign.?in|forgot.?password)" -title -sc -silent
# Or match by page title
katana -u https://target.com -silent | httpx -title -ms "Login" -sc -silent
# Broader — catch login, signin, auth pages
katana -u https://target.com -silent | httpx -mr "(?i)(log.?in|sign.?in|type=.?password|authenticate)" -title -sc -tech-detect -silent
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thank you for your answer, it was helpful. I will use what you wrote for verification in this process. I'm thinking of using Playwright for full verification here. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to detect login pages using HTTPX? Generally, when we output a katana file to HTTPX, can it identify the login page directly by checking the first page that appears, using fields like username and password? There's a feature called
-fpt loginthat does the reverse, but is there a feature I can use to detect the login page in the opposite way? Or what would you recommend in this regard?Beta Was this translation helpful? Give feedback.
All reactions