mirror of
https://github.com/itepechi/har2vegeta.git
synced 2025-05-09 15:06:41 +00:00
docs(README): tell people to isolate the attacking PC as well
This commit is contained in:
parent
594b646c79
commit
c90a2128f5
1 changed files with 8 additions and 4 deletions
12
README.md
12
README.md
|
@ -1,5 +1,8 @@
|
|||
# har2vegeta – Convert HAR files to a Vegeta compatible format
|
||||
|
||||
> A barely realistic benchmark is still better than an unrealistic benchmark.
|
||||
> – Nobody
|
||||
|
||||
## Install
|
||||
|
||||
```sh
|
||||
|
@ -11,8 +14,9 @@ cargo install --path .
|
|||
Export your HAR file from the Network tab of your browser's DevTools and run the
|
||||
command as shown below.
|
||||
|
||||
I highly recommend isolating the target machine (which should be yours, of
|
||||
course) from the public Internet before launching the attack.
|
||||
I highly recommend isolating the source and target machine (which should be
|
||||
yours, of course) from the public Internet before launching the attack, to
|
||||
prevent connections from going out.
|
||||
|
||||
```sh
|
||||
cat your_file.har | har2veg | vegeta attack ...
|
||||
|
@ -26,10 +30,10 @@ The format to output. The HTTP format is more human readable, but it can only
|
|||
handle request bodies by adding a reference to real files. **har2veg** will
|
||||
automatically export bodies to temporary files, but will not delete them after
|
||||
running **Vegeta** because there's no realistic way to implement it. The JSON
|
||||
format is the recommended format if you want to pipe directly to **Vegeta**
|
||||
format is the recommended format if you want to pipe directly to Vegeta
|
||||
because it supports embedding base64 encoded bodies.
|
||||
|
||||
This option defaults to the HTTP format to be consistent with **Vegeta**'s
|
||||
This option defaults to the HTTP format to be consistent with Vegeta's
|
||||
default.
|
||||
|
||||
## License
|
||||
|
|
Loading…
Reference in a new issue