This repository has been archived by the owner on Aug 31, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 29
Configuring Custom Headers
Scott Behrens edited this page Jul 24, 2017
·
1 revision
This page describes how you can configure custom headers for your test.
By default, the following header file is used in all requests:
{"Connection": "close", "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0", "Accept": "application/json, text/javascript, */*", "Accept-Language": "en-US,en;q=0.5", "Accept-Encoding": "gzip, deflate", "Content-Type": "application/json", "Cookie": ""}
You can create your own custom header file as long as your file is a key/value hash. Header files are loaded from the header/
folder located in the project root.
Here's an example of a custom header file we crated in the headers
folder.
{"Connection": "close", "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0 GRIZZLY TEST contact company@company.com for more info", "Accept": "application/json, text/javascript, */*", "Accept-Language": "en-US,en;q=0.5", "Accept-Encoding": "gzip, deflate", "Content-Type": "application/json", "Cookie": "$$AUTH$$"}
You will notice the $$AUTH$$
placeholder which will tell Repulsive Grizzly where to place authentication objects it loads in.
- Home
- Installation Guide:
- Configuration:
- Cloudy Kraken Configuration:
- Grizzly Tracker