According to Brandon W. Uhlman:
> > OK, I'd start by making sure the IIS server is set up to allow running
> > CGI scripts from the directory in which you've placed the htsearch.exe.
> > If other CGI scripts in the same directory give the same error, that's
> > a good indication of a server configuration problem. If I recall,
> > IIS expects all CGI scripts to emit full headers, as non-parsed-header
> > (nph) scripts do, so you'll probably need to set the nph attribute in
> > your config file to true. I don't know what else to suggest, given
> > my unfamiliarity with NT. Perhaps others on the list with NT know-how
> > could shed more light.
>
> Okay, this problem is now fixed. Turns out I was calling "htsearch" instead
> of htsearch.exe. Go figure. Now its telling me about Incomplete Headers.
>
> This is the full text:
>
> CGI Error
> The specified CGI application misbehaved by not returning a complete set of
> HTTP headers. The headers it did return are:
>
>
> ====
>
> Yes, that's right. It returned no headers.
>
> Run from a command prompt, it asks me for a query string (in so many words),
> and then returns the results of a successful search, with what looks like a
> complete (and correct) http header. Thoughts?
By a complete http header, do you mean it starts with these two lines?
HTTP/1.0 200 OK
Content-Type: text/html
You did set "nph: true" in your config file, right? If so, have a look at
your IIS documentation to see what it considers to be complete headers.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
