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.

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

Add some CLI options #158

Closed
wants to merge 134 commits into from
Closed

Add some CLI options #158

wants to merge 134 commits into from

Conversation

rsrdesarrollo
Copy link

fix #103. fix #137. fix #29. Add CLI options to specify headers, proxy and basic authentication whitout the need of touching config file

epinna and others added 9 commits August 13, 2020 22:48
- _check_openbasedir() returned a broken value
- open_basedir separator choice was wrong
- display was quirky
New info `server_ip` has been added to `results_to_store`.
An argument has been added to `:system_info`: `-extended`. It enables new info to be gathered (as it can be a bit slow to gather everything).
As `:system_info` now has too many values for its `-info` argument to let argparse build it's metavar. Metavar is now empty and possible values are displayed in help text.
* Add missing comma in `proc_manipulation`
fixes `DH_KEY_TOO_SMALL` error
@rsrdesarrollo
Copy link
Author

This PR adds the following CLI options to the terminal command

  -H HEADERS, --header HEADERS
                        (HTTP) Extra header to include in the request. This option can be used multiple times to add/replace/remove multiple headers.
  -x PROXY, --proxy PROXY
                        Use a specific proxy [protocol://]host[:port].
  -u USER, --user USER  <user:password> server user and password for basic auth

the interface is the same as curl

@ZanyMonk
Copy link
Collaborator

ZanyMonk commented Jun 10, 2023

Good idea !

There is one thing that bothers me though : there is no default=[] for headers, it's None when starting a new session and that raises an Exception. Could you add a default value to this argument please ?

@rsrdesarrollo
Copy link
Author

rsrdesarrollo commented Jun 21, 2023

Sorry I fu%k%d up my repo (for reasons I'm ashamed to tell) xDD, I will generate a new PR, is easier than recovering the history of my broken repo xD

@noraj
Copy link
Contributor

noraj commented Apr 8, 2024

@rsrdesarrollo I would be nice you PR this again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet