RE: Re[2]: [cobalt-users] Help with simple CGI.

[Liz <daldog@xxxxxxxx>]

Thanks for correction on parsing.  One learns something new
everyday! <smile>

CGIWrap has it's good points, yes, but debugging cgi scripts
with the wrapper is big headache.  I'm sure other's can
relate to this...but there have been countless times I setup
various scripts which run perfectly normal on a regular old
RedHat60 PC server minus the cgiwrap. As soon as that same
scripts are ran on a Cobalt with the wrapper enabled, most
scripts encounter a problem of some type.  Yet if I do a
perl -c script.cgi I get syntax OK, or looking at the error
log not much bug detail info is recorded.  Is there a better
way to debug scripts with the wrapper enabled?

What's the deal with "wrapper not found" error filling up my
error log?  Even if the script doesn't have a bug...or if
it's a basic script that has only a line such as: print
"hello world";
that "wrapper not found" continues to clog up the log. 
There's got to be a way to fix this.



------Original Message------
From: Allan Liska <support@xxxxxxxx>
To: cobalt-users@xxxxxxxxxxxxxxx
Sent: January 28, 2000 5:24:28 AM GMT
Subject: Re[2]: [cobalt-users] Help with simple CGI.


Hello Liz,

Actually, Apache will server-parse whatever files you tell
it to.  Its
generally considered a bad idea to server parse all HTML
though,
because that places an unnecessary burder on the server.

To set up server parsed HTML you need to edit:

/etc/httpd/conf/srm.conf

To enable it for all sites on the server simply uncomment:

#AddType text/html .shtml
#AddHandler server-parsed .shtml

(you can do this on a site-by-site basis in the control
panel).

Also, I disagree with regard to your dislike of CGIWrapper. 
It
actually makes a lot of sense, especially in a shared
environment.  By
executing scripts within the CGIWrapper environment you can
keep one
run away perl script from hosing your entire box.


Thursday, January 27, 2000, 10:59:50 PM, you wrote:

L> All cgi errors are suppose to be logged in your error
log,
L> located in /home/log/httpd/error.  Telnet in and do a
"tail
L> -10 error" to see the last 20 entires in the error log.
L> Check there for a little more detail about what kind of
L> error you're receiving instead of the generic server
L> response for all "Internal Server Errors".  Or you can
type
L> the following in telnet too:  perl -c yourfilename.cgi

L> Due to CGIWrap which comes installed on the RaQ3,
debugging
L> scripts is a major pain in the butt.  I personally hate
that
L> wrapper and am about ready to send it's suitcase a
packing.

L> I believe Apache requires the .shtml file extension in
order
L> to parse the file.  Details on SSI can be found at
L> www.apache.org or www.apacheweek.com

L> Liz


Best regards,

allan

--
Allan Liska                                    703-443-6754
allan@xxxxxxxx                                
http://www.priz.net
"Looking at the proliferation of personal web pages on the
net, it
looks like very soon everyone on earth will have 15
Megabytes of fame."




_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-users

______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com?sr=mc.mk.mcm.tag001