August 4, 1999 - Osmosis Technical Note 8

Subject: Foreign Scripting

Problem:

Note - Definition "Foreign Script" - We refer to a foreign script as one which was created by an application other than Osmosis. For example, an AppleScript or Frontier script is 'foreign' with reference to an Osmosis script.

Using a foreign script to launch Osmosis, the script does not run or prematurely aborts. When checking the Osmosis error log, the following message is displayed, “Osmosis Error: Sending Header to Web Server”.

Discussion:

Osmosis is sending data back to the script when it reaches the ENTRY step. Since most scripts are not prepared to receive such data, Osmosis reports an error and aborts.

Open the Osmosis script and carefully review the ENTRY step parameters. You will notice a field called, "Custom Header". This entry tells the web server (or in this case, the foreign script), that the output will be HTTP (content type/text html). When communicating with the web server, this is required - and the web server expects it. A foreign script does not need this information.

Solution:

The Custom Header field appears blank to the user, however Osmosis automatically sends the HTTP header - by default.

To override this default behavior, place any single alpha character into the Custom Header field. Osmosis will then omit the header.
___________

We appreciate the efforts of Lenny Eiger of DataBright Management Systems in helping to resolve this problem.