WAPITI-GETCOOKIE(1)

πŸ“¦
version 3.2.10 Β· 2 versions
, in ubuntu resolute

πŸ’– WAPITI-GETCOOKIE(1) β€” General Commands Manual πŸ’–

okay bestie, pull up a chair, we're doing wapiti-getcookie from the wapiti-getcookie(1) manual page and it's genuinely so useful. no cap.


✨ NAME ✨

wapiti-getcookie β€” a Wapiti utility that goes and fetches cookies from a webpage, then tucks them away safely in the Wapiti JSON format. πŸͺ


🌸 SYNOPSIS 🌸

wapiti-getcookie -u URL -c COOKIE options

πŸ¦‹ DESCRIPTION πŸ¦‹

wapiti-getcookie is a user-friendly interactive console utility β€” yes, interactive, it literally talks to you πŸ’… β€” that you can use to fill in a web-form or fetch a URL, and then it extracts the cookies the remote server sends back.

All that cookie info gets stored in the JSON cookie file, and you have to tell it which file with the -c option. no -c, no cookies, periodt.

And the slay part? Wapiti itself can load those exact same cookies using the same -c option. so it's one little handshake between this tool and the scanner. iconic. πŸ”₯


πŸ‘‘ OPTIONS πŸ‘‘

  • -p, --proxy PROXY_URL β€” whatever URL you hand over gets used as a proxy for HTTP and HTTPS requests. The URL can use one of these schemes: http, https, socks. And if you wanna make Wapiti go through a Tor listener, you use --proxy socks://127.0.0.1:9050/ πŸ§…
  • --tor β€” makes Wapiti use a Tor listener. same thing as --proxy socks://127.0.0.1:9050/, just the short way of saying it. 🌈
  • -a, --auth-cred CREDENTIALS β€” sets the credentials to use for HTTP authentication on the target. The value you give should look like login%password β€” yeah, % is the separator. wild, but that's the vibe. πŸ”
  • --auth-method TYPE β€” sets which authentication mechanism to use. Valid choices are basic, digest and ntlm. heads up: NTLM authentication may require you to install an additional Python module. πŸ’€
  • -H, --header HEADER β€” sets a custom HTTM header to inject into every request Wapiti sends. You can use this option several times (stack 'em up, bestie). The value should be a standard HTTP header line, with the parameter and value separated by a : sign. πŸ“¨
  • -A, --user-agent AGENT β€” Wapiti's default behavior is to use the same User-Agent as the TorBrowser, which keeps it discreet when it's crawling standard websites or .onion ones. But sometimes you've gotta change it to bypass some restrictions, so this option is here for you. πŸ•΅οΈβ€β™€οΈ
  • -d, --data DATA β€” wapiti-getcookie will parse forms and ask for your input on every field it finds. But you can also just pass every parameter and value as a string directly through this option. Example: -d 'login=admin&password=letmein&submit=Login' ✨

πŸ’œ LICENSE πŸ’œ

Wapiti is covered by the GNU General Public License (GPL), version 2. Please read the LICENSE file for more info, fr fr. πŸ“œ


Copyright (c) 2006-2023 Nicolas Surribas.


🌟 AUTHORS 🌟

Nicolas Surribas is the main author, but the whole list of contributors lives in the separate AUTHORS file. give them their flowers πŸ’


🌐 WWW 🌐

https://wapiti-scanner.github.io/


πŸ› BUG REPORTS πŸ›

If you find a bug in Wapiti, please report it to https://github.com/wapiti-scanner/wapiti/issues β€” they wanna know, bestie. πŸ™ˆ


lowkey the most important rule of this whole page: use -c to save the cookies, then use the same -c to load them into Wapiti. that's the whole plot. πŸ’–

and that's a wrap! this page came from the wapiti-getcookie(1) manual, dated April 2026 🌸 β€” mwah, go grab some cookies πŸͺπŸ’…

πŸ“¦ where this page comes from