Here are a few suggestions... 1) If you're going to quote an archived message, you should include an URL to the message, or at least include the date of the message, to make it easier to find. This particular message was from almost 3 1/2 years ago (3 May 1999). How good do you expect a busy man's memory to be?
2) It often helps to read the whole thread carefully. I gave Jorge some suggestions on how to track down the error. He never got back to me. The ball was in his court. It was his problem to solve. If he did, he didn't tell me about it, so your question might be better directed to him than to me. If an internal server error can be pinned down to a bug in htsearch, we'll certainly try to fix the bug, but without any server error log messages to look at it's impossible to pin down the error to anything, let alone a bug. 3) Check the FAQ. There are a few entries dealing with internal server errors: http://www.htdig.org/FAQ.html#q5.7 http://www.htdig.org/FAQ.html#q5.13 and http://www.htdig.org/FAQ.html#q5.14 Generally, the error means htsearch aborted before outputting any header. You need to find out why it's aborting on your system. 4) Keep ht://Dig related questions on the appropriate mailing list, please. See http://www.htdig.org/FAQ.html#q1.16 and 1.17 According to Ochs, Paul C: > Did you ever solve this? > > > > According to Jorge: > > I'm using htdig with Apache_1.3.3 web server and this morning, when I > > try to do a search, appears this error in my Browser: > > > > ---------------------------------------------------------------------- > > Internal Server Error > > > > The server encountered an internal error or misconfiguration and was > > unable to complete your request. > > > > Please contact the server administrator, [EMAIL PROTECTED] and inform > > them of the time the error occurred, > > and anything you might have done that may have caused the error. > > > > Premature end of script headers: /home1/apache_1.3.3/cgi-bin/htsearch > > > > > > Apache/1.3.3 Server at nuevo.conferco.es Port 80 > > ---------------------------------------------------------------------- > > > > Somebody know why this is happening? > > Premature end of script headers usually means that htsearch died before > outputing its "Content-type: text/html" header. Check the server error > log to see if it gave any error messages at that time. If that doesn't > help, try running htsearch in interactive mode, from the command line, > to see if it dies that way too. If you get a core dump, get a stack > backtrace from the debugger to see where it's dying. > <<...OLE_Obj...>> > -- 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: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
