File hierarchy - acastaner/harhar GitHub Wiki

When Harhar is executed, a directory is created in the same folder that holds the executable. For instance, if Harhar is in E:\har the folders will be created in that directory. The folder hierarchy is the following:

<root directory holding harhar.exe>
<execution_date>
	<har_file_name>
		<hostnames>
			<resource_uri>
				<resource_file>

For instance, the file “http://www.spirent.com/spirentAssets/images/bullets.gif” that was found in the file www.spirent.com.har and executed on March 28th 2014 at 9h46 min 34s will be stored here:

E:\har\3-28-2014_9-46-34\www.spirent.com.har\www.spirent.com\spirentAssets\images

We preserve the hierarchy because this way you can re-upload these files as a Transaction Profile in the Avalanche Commander GUI as “Files from a directory” - and keep the correct hierarchy. This is useful because it keeps the same URLs when replaying the traffic, which might be important for the Devices Under Test.

A few other files are created under the “har_file_name” directory: urls.txt and action_list.txt. The first file is simply a list of all the requests that we parsed (you could conceivably use it with wget or curl for other uses).

The second one is an Avalanche Action List that you can copy/paste into Avalanche Commander. Any header not mandatory in HTTP 1.1 (like Connection: ; Host:, etc..) is included using the ADDITIONAL_HEADER command. The mandatory headers are not added because Avalanche automatically adds them. Be careful with this action list because cookies, being headers, and other headers that might contain authentication.

⚠️ **GitHub.com Fallback** ⚠️