According to Gabriele Bartolini:
> Here is the description for cookies_input_file:
>
> "Set the input file to be used when importing cookies for the crawl;
> cookies must be specified according to Netscape's format (tab separated
> fields).
> For more information, give a look at the example cookies file (cookies.txt)
> distributed with ht://Dig. By default, no input file is read."
Here's my edited version:
{ "cookies_input_file", "", \
"string", "htdig", "", "3.2.0b4", "Indexing:Connection", "cookies_input_file:
${common_dir}/cookies.txt", " \
Specifies the location of the file used for importing cookies \
for the crawl. These cookies will be preloaded into htdig's \
in-memory cookie jar, but aren't written back to the file. \
Cookies are specified according to Netscape's format \
(tab-separated fields). If this attribute is left blank, \
no cookie file will be read. \
For more information, see the sample cookies.txt file in the \
ht://Dig source distribution. \
" }, \
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada)
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev
