According to Randall Fish: > I am getting a CGI Error from the web browser when I perform a search. > > 'The specified CGI application misbehaved by not returning a complete set of > HTTP headers. The headers it did return are:' > > This is the header that htsearch is returning when I run it from the command > line: > HTTP/1.0 200 OK > Content-type: text/html > > I have the 'nph' variable set to true in my config file (as you could > probably tell by the header generated). > > htsearch works the way it's supposed to on our development server which is > non-ssl (http) but it returns the error on the test server which is ssl > (https). > > I do not have in-depth knowledge of HTTP headers but could this article by > M$ have something to do with my problem? > http://support.microsoft.com/default.aspx?scid=kb;EN-US;q187504 > > This is version 3.1.5 installed on an NT4.0 server with IIS4.0.
I don't think so. This article deals with HTTP 1.1 host headers, but htsearch is strictly using HTTP 1.0, and I don't think it would care about host headers anyway, as these are up to the web server to deal with. Are you implementing multiple virtual servers under IIS's SSL support "using the same IP address and port number, but using HTTP 1.1 host headers"? If not, then I don't think this applies. If so, then perhaps this might cause IIS not to know how to locate and run the htsearch CGI properly for this particular virtual host. You say that the error you get from the web server is: '... The headers it did return are:' but does it show any headers there? If not, then it would seem that htsearch isn't running properly under your IIS SSL server. If it is showing the same headers that you get from the command line, the problem would seem to be that IIS doesn't consider these two headers a complete set when running under SSL, so you'd need to find out what is. > Does anybody have any suggestions on how to resolve this problem? > > I'm thinking about trying to install the 3.2.0b3 version but I would like to > get one version working before I start experimenting. Has anybody else > installed 3.2.0b3 on an NT machine? Any tips? Well, if you want to try a 3.2 beta, don't waste time on 3.2.0b3, but instead grab a recent 3.2.0b4 snapshot from http://www.htdig.org/files/snapshots/ However, the header handling hasn't changed recently. So, unless the problem is caused by htsearch dying prematurely, I don't know that 3.2.0b4 or 3.1.6 would help with this particular problem. It would still be a good idea to upgrade to one of these, though, for all the other bug fixes. -- 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) _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ 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
