v1.3.0

[buger]

Highlights

Added official Windows support https://github.com/buger/goreplay/wiki/Running-on-Windows

Traffic capture engine fully re-constructed to be more scalable, efficient and bulletproof.
You should see way lower packet loss, capture quality, and CPU/Memory usage.

Deprecated own HTTP client in favour of native Go HTTP library #833

Increased stability, and numerous bug fixes.

Features

• Added way to capture traffic from multipe ports with single input --input-raw :80,8080,3000 capture list of ports in a single listener #935
• Added --output-tcp-skip-verify flag to skip TCP output TLS verification Added flag to skip hostname verification #814 @tomerf
• Added --output-tcp-workers to configure number of TCP output connections Make the number of TCP connections configurable #819
• Added new debugging endpoint when --http-pprof enabled: /debug/vars
• Added new %i file name variable to inject unique instance ID to file name. Can be useful if you have logs from multiple machines and you need unique names.
• Added --input-file-dry-run option to previewing how long it will take and how many requests in given file input 8e76559
• Added --input-raw-max-wait option (in seconds), which allows to skip long pauses in recorded files 19ad90a
• Added --input-file-read-depth option to pre-read and buffer requests (and sort them). By default, is 100 625ed54
• Added --input-raw-timestamp-type go to enable application level timestamps, when network timestamps unreliable 8edb74e

Thank you, @urbanishimwe, @slimus, @arijitAD for jumping with me to this adventure!

Huge kudos to all GoReplay community, especially to our contributors
@DimaGolomozy @tomerf @swills @davidFR @two @jl2005 @rmasclef @othererik @ankitdobhal @eko @code4wt @wangfeng22 @lins05
@betty1126 @YuriYin @StanleyP

---

This discussion was created from the release v1.3.0.