Below is an example which will send requests to two endpoints (`127.0.0.1:80` and `127.0.0.2:80`), while alternating between two request headers which contain different paths and hosts.

This example has been useful to test a mesh that exposed multiple endpoints, which in turn would offer access to multiple applications via different hosts/paths.

This example illustrates the following features:

- [Request Source](https://github.com/envoyproxy/nighthawk/blob/261abb62c40afbdebb317f320fe67f1a1da1838f/api/request_source/request_source_plugin.proto#L15) (specifically the file-based implementation).

- [Multi-targetting](https://github.com/envoyproxy/nighthawk/blob/261abb62c40afbdebb317f320fe67f1a1da1838f/api/client/options.proto#L84)

Place a file called `traffic-profile.yaml` in your current working directory. This will act as your configuration for the file-based request source.

options:

- request_method: 1

request_headers:

- { header: { key: ":path", value: "/foo" } }

- { header: { key: ":authority", value: "foo.com" } }

- request_method: 1

request_headers:

- { header: { key: ":path", value: "/bar" } }

- { header: { key: ":authority", value: "bar.com" } }