[ale] Apache and GCI echo server (UPDATE)

Sun Nov 26 21:50:24 EST 2006

I think the difference is that minimal web servers like thttpd and
GoAhead simply use select to pass data between the browser and any cgi
program.  Apache is more restricted in what it will do.  In a GET it
will expect all output from the CGI then when the CGI dies it will pass
that output to the browser.  A POST probably works in the opposite
direction.  Get all output from the browser then execute CGI and pass
that output to it.  The only option I can see is a httpd.conf parameter
that will allow me to tell it on certain pages to simply use select to
pass data between the browser and the cgi.  Not even sure of that is
possible...

On Sun, 2006-11-26 at 10:25 -0500, Christopher Fowler wrote:
> Apache is doing its own processing.  When I left the computer and came
> back I got the following error message from the server:
> 
> 
> [tomcat at sam-devel SystemConfig]$ telnet 127.0.0.1 80
> Trying 127.0.0.1...
> Connected to 127.0.0.1.
> Escape character is '^]'.
> GET /SC/echo.pl
> Echo this line
> 
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>500 Internal Server Error</title>
> </head><body>
> <h1>Internal Server Error</h1>
> <p>The server encountered an internal error or
> misconfiguration and was unable to complete
> your request.</p>
> <p>Please contact the server administrator,
>  you at example.com and inform them of the time the error occurred,
> and anything you might have done that may have
> caused the error.</p>
> <p>More information about this error may be available
> in the server error log.</p>
> <hr>
> <address>Apache/2.0.55 (Unix) mod_ssl/2.0.55 OpenSSL/0.9.7a mod_jk/1.2.5
> Server at sam-devel.opsup.com Port 80</address>
> </body></html>
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale