On Thu, 23 Oct 2003 21:51, Gabriele Bartolini wrote:

>     can you please revise the defaults.cc documentation for the
> 'head_before_get' attribute. I wrote something but it needs some
> revision by english mother-tongue developers.

Your English is fine.  I've made a few changes below, if you're 
interested (but it was OK as it was).

Cheers,
Lachlan

If set to true, an HTTP/1.1 <em>HEAD</em>
call is made in order to retrieve header information about a document.
If the status code and the content-type returned show that the 
document is parsable, then a subsequent 'GET' call is made.  In 
general, it is recommended that this attribute be set to 'true',
as it can really improve performance (especially when used with 
persistent connections).  This is particularly so during an 
incremental dig, since in this case 'htdig' can ask the server if the 
document has been modified since last dig. However there are a few 
cases when it is better to switch it off:
<ul>
<li>the majority of documents are parsable (HTML or a type for which 
an external parser has been provided) and must be retrieved anyway 
(initial dig);</li> 
<li>the server does not support the HEAD method or it is 
disabled;</li> 
<li>in some cases persistent connections
(<a href=\"#persistent_connections\">persistent_connections</a>) may 
not work properly and either the 'head_before_get' attribute or the 
'persistent_connections' attribute must be turned off.
</li>
</ul>

-- 
[EMAIL PROTECTED]
ht://Dig developer DownUnder  (http://www.htdig.org)


-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to