According to Gabriele Bartolini:
> However, I would pick these general cases, where the user should disable 
> the attribute (please revise it):
> 
> Case A - Persistent connections on
> 1) the majority of documents are HTML (this means we "always" want to GET them)
> 2) the server does not support HEAD (I have seen cases like this unfortunately)

OK, that sounds pretty important.  I hadn't heard that one before.
Persistent connections are only on for HTTP/1.1 servers, so what you're
saying is that there are servers out there that claim to be 1.1 compliant
but don't support the HEAD request.  Wouldn't this be an argument against
overriding head_before_get during an incremental dig?

> 3) cases where the persistent communication between htdig and the server 
> does not work at 100%: there can be some problems with persistent 
> connections and HEAD calls (I experience this kind of problems sometimes 
> with ht://Check and some NT servers)

Again, is this going to be a problem if we don't allow turning off
head_before_get during an update dig?

> Case B - Persistent connection off
> 1) same as case A
> 2) same as case A

In this case, the server could be HTTP/1.1 or 1.0.  Either way, the same
question applies.  If the user needs a way to tell htdig to deal nicely
with these questionably compliant servers, then wouldn't they need a way
of turning off head_before_get unconditionally, whether it's an update
dig or an initial one?

This is what I was getting at before about this option never being
explained adequately.  On the surface, it seemed to be rather useless,
but with these new revelations that have come out of your testing, it
seems there may indeed be a need for turning this off in some cases.
That's the sort of thing that should be documented so others (developers
and end-users) know what you'd use this for.

-- 
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 OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to