On Thu, 18 Jul 2002, Ian! D. Allen [NCFreeNet] wrote:

> I have some CGI scripts that generate index pages.  Dear htdig refuses
> to execute these scripts, saying they are "non local" and giving the

No, this is correct. You're using the local_urls feature, so the local
filesystem will be checked first before trying HTTP. A CGI script is *not*
something to parse directly, so it really is "non local" from the
standpoint of needing to hit the HTTP server.

> If the URL is already classified as a "local filename", one should not
> second-guess that classification by checking local_urls_only, since a
> failure to retrieve a local file from the file system does *not* mean
> that the file is non-local - it may mean that the item is a local CGI

If you have a better idea for what the error message should be, that's
fine. The htdig program is not going to execute the CGI directly, whether
it's actually on your drive or not--so it's going to defer to HTTP and get
the server to set up the CGI environment properly.

> script that should be executed.  The error "host not found" is wrong -
> do not use the status 'Transport::Document_no_host' here.

No, I disagree. Perhaps it should spit up a specific error message if
you're using local_urls_only as you seem to be here. But you've told
ht://Dig not to revert to HTTP, but it must. I'd call this "no host for
HTTP transaction."

If you disagree, please offer some better suggestions. I see this as doing
exactly what it's supposed to do. Unless you or someone else donates code
to run local CGIs like a full HTTP server does, CGIs will revert to HTTP
transactions.

--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/






-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to