PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: travis dot winfrey at gs dot com (Travis Winfrey - NY)
Subject: Re: Hi All
Date: Dec 5 1995 5:27PM

> I am integrating sybperl with a web/cgi script and it runs fine on the
command
> line, but dies with 'ERROR 500, malformed header'. I call &dbuse and &dblogin
> prior to printing the cgi header, and I think the problem rest in the system
> call (or maybe how my sybperl is situated in the web directory (it is
included
> in the server root path)

The Contents-Type line must be the very very first line of output from
any CGI script, or any HTTPD daemon will nuke it immediately.
in this case, there's no reason not to put that line first, since you
can give a nicely formatted html error message.

You could also install a message handler.  This could redirect
to a file or stderr, or suppress some messages based on their severity.
ordinary PRINT commands from sql and dbuse informational messages are
both severity 1.

t