CGI Fiction Search Example

Gregory Lypny gregory.lypny at
Thu Sep 2 12:12:49 EDT 2004

Hello Jacqueline,

I found the error log.  Here are the last errors for Fiction Search and 


[Thu Sep  2 10:20:31 2004] [error] [client] Premature end of 
script headers: /Library/WebServer/CGI-Executables/

[Thu Sep  2 10:25:18 2004] [error] [client] Premature end of 
script headers: /Library/WebServer/CGI-Executables/

On Sep 2, 2004, at 12:00 PM, use-revolution-request at 

> Message: 14
> Date: Thu, 02 Sep 2004 10:20:54 -0500
> From: "J. Landman Gay" <jacque at>
> Subject: Re: CGI Fiction Search Example
> To: How to use Revolution <use-revolution at>
> Message-ID: <41373A56.10603 at>
> Content-Type: text/plain; charset=us-ascii; format=flowed
> On 9/2/04 9:22 AM, Gregory Lypny wrote:
>> Hello everyone,
>> I'm trying to run Jacqueline Landman Gay's Fiction Search CGI example 
>> on
>> my iBook.  I think I've set the correct file permissions for the files
>> in the CGI bin; everything is read-write.  But when I try to do a 
>> search
>> in my browser, it loads for a very long time and then I get the
>> following internal server error (no. 500):
>> ---------------- copied from browser---------------
>> Internal Server Error
>>  The server encountered an internal error or misconfiguration and was
>> unable to complete your request.
>>  Please contact the server administrator,  [no address given] and 
>> inform
>> them of the time the error occurred, and anything you might have done
>> that may have caused the error.
>>  More information about this error may be available in the server 
>> error
>> log.
>> Apache/1.3.29 Server at hurricane.local Port 80
>> ---------------- end of copied from browser---------------
>> The same thing happens when I try to run her  What am I 
>> doing
>> wrong?
> There isn't any way to know until you look at the system log. What OS
> are you on? If it is OS X, the log is located at:
> /private/var/log/httpd/error_log
> You may have to use the Finder's "Go" menu to type in the path since
> those folders are normally invisible on OS X. I usually place an alias
> to the error log on my desktop so I can open it easily while I'm 
> debugging.
> The last reported error will be at the bottom of the log. If there is a
> scripting error, the engine will provide a clue to the command that
> failed. If there is an installation or permission error, you'll see 
> that
> too.

More information about the use-livecode mailing list