Pls read _carefully_ my comments and hints below.
On Aug 30, 1:38 pm, donpro <
donpro-2...@rogers.com> wrote:
> You are correct. I have made the changes but it has ot helped
What does not helped? Have you downloaded the fs4web.tar example,
compiled on the Linux system and run as described in the how-to and as
I previously suggested? How did you compile? According to your
postings, you are not using these supplied examples, since the the
"example1.sh" is formatted correctly in the tar archive.
On Aug 30, 1:41 pm, donpro <
donpro-2...@rogers.com> wrote:
> I have saved the script, webbook.sh as UNIX but am still getting an
> Internal Service Error with the single log file message: Premature end
> of script headers: webbook.sh
> How do I manually add a NewLine to a file? Should I try to save in PC
> or MAC format?
How about vi (on the server) ?
> Alternatively, can FlagShip be run from the web as non compiled same
> as PHP, something like #include webbook.prg. This would also solve my
> problem
FlagShip is native compiler, not an interpreter like PHP. As stated in
the above how-to, you MUST compile your application statically by the
Pro version of FlagShip corresponding to the target system (in your
case: by FlagShip for RedHat Linux). Again: re-read the how-to and
check first by the example.
Generally: To check if your Apache is configured correctly, create in /
cgi-bin directory (on the server) file named webbook.sh containing:
#!/bin/bash
echo 'Content-Type: text/html'
echo ''
echo '<html><head>my cgi test</head><body>'
echo 'Hello world!<p> </p>'
echo '</body></html>'
set it permission to 755 and then invoke/submit (by any browser) your
HTML file containing the line
<FORM ACTION="/cgi-bin/webbook.sh" METHOD="get">
The above webbook.sh script on the server will/should then simply
reply with "Hello world!" displayed in your local browser. If not so,
it is something wrong with your settings, since it is fully
independent on the FlagShip's executable. In such a case, contact your
system or server administrator. For FlagShip support, best to contact
directly <support -at- flagship -dot- de>
Paul