Comment on page
Inspect traffic to web applications with a HTTP reverse proxy
The proxy tool allows to quickly spin up monitoring of web applications and retrieving netcap audit records.
Since currently, TCP stream reassembly is only supported for IPv4, netcap misses HTTP traffic over IPv6 when decoding traffic from raw packets. Also there is currently no support implemented for decoding HTTP2 over TCP or QUIC.
By using a simple reverse proxy for HTTP traffic, the operating system handles the stream reassembly and we can make sure no IPv6 and / or HTTP2 traffic is missed.
Spin up a single proxy instance from the commandline:
$ net proxy -local 127.0.0.1:4000 -remote http://google.com
Specifiy a custom config file for proxying multiple services with the -proxy-config flag:
$ net proxy -proxy-config example_config.yml
The default config path is net.proxy-config.yml, so if this file exists in the folder where you execute the proxy, you do not need to specify it on the commandline.
For proxying several services, you need to provide a config file, here is a simple example:
# Proxies map holds all reverse proxies
# CertFile for TLS secured connections
# KeyFile for TLS secured connections
# Logdir is used as destination for the logfile
Usage of net proxy:
print netcap package version and exit
set config file path (default "net.proxy-config.yml")
set debug mode
seconds until dialing to the backend times out (default 30)
seconds until a connection times out (default 90)
set local endpoint
maximum number of idle connections (default 120)
set remote endpoint
skip TLS verification
seconds until a TLS handshake times out (default 15)