You can configure your project to automatically apply one or more cookies before crawling commences. This can be used to provide authentication cookies in the event that the built in authentication features of WebCopy are not sufficient.
Cookies stored in a WebCopy project must conform to the Set-Cookie header syntax. The minimum required is <cookie-name>=<cookie-value>. <cookie-value> should be URL encoded if appropriate, WebCopy does not perform any automatic encoding.
If you use Forms, Passwords or Cookies to authenticate with a website, you should consider adding a custom rule to exclude any logout pages. Otherwise, if WebCopy detects this page, eventually it will access it and your session will be logged out, potentially affecting the remainder of the crawl.
To read cookies from an external file, enter the file name in the Read Cookies From field, or click the Browse button to select a file.
Only cookies in the Netscape cookie file format are supported.
To discard any session cookies from the external file, ensure the Discard session cookies option is checked. When set, any cookies without an expiry date will be skipped.
Once a copy operation has complete, WebCopy can optionally write all cookies into a file, using the Netscape cookie format. To write cookies to a file, enter the file name in the Write Cookies To field, or click the Browse button select a file.
Cookies are only written when performing a copy, not when performing a read-only scan.