10 Compiling, linking, and installing your WebKit program

Contents of this section

Note: Upon startup, a FlagShip application tries to create a temporary file in the current directory. For that reason, you cannot execute a FlagShip application without having write access to the current directory. When httpd executes an application via CGI, though, it is in the cgi-bin directory. There are some obvious security and configuration problems with giving httpd write access to its own cgi-bin directory.

So, as a workaround, the webkit script saves its current directory information (so it can find its own binaries) and changes to a directory whose name is specified in the WebKit configuration file before running the WebKit application.

A Gateway-mode server must be loaded (from the command line or rc.local or whatever) before it's invoked from CGI. WebKit will not do this for you. The program will initiate the Gateway-mode program and return to the shell prompt. Your application will have the access rights of the effective userid under which it was started. If this does not happen, you will need to check the output from syslog for information and error messages.

Next Chapter, Previous Chapter

Table of contents of this chapter, General table of contents

Top of the document, Beginning of this Chapter