HTTP_RESPOND_FILE

This activity may be used to send a file in response to an inbound HTTP request.

The activity is valid only with an inbound HTTP session – that is one that was initiated using the HTTP_BEGIN_INBOUND activity.  For more information on inbound HTTP processing in LANSA Composer, refer to:

HTTP Inbound (Server) Processing in LANSA Composer

INPUT Parameters:

HTTP_HANDLE: Required

This parameter must specify the session handle value that identifies the HTTP session upon which this activity should operate.  The session handle value is returned by the HTTP_BEGIN_INBOUND activity.

HTTP_RESPONSEFP: Required

This parameter must specify the path and file name of the file to be sent in response to te inbound HTTP request.

HTTP_RESPONSECT: Optional

This parameter is optional. If it contains a non-blank value it will be used as the content type.  If this parameter is not provided or the special value *AUTO is specified, then the content type will be derived from the file extension of the file being sent.  (This is achieved by a lookup on the file filetype.txt in the <system> directory of the server's JSM instance directory tree.)

Refer to the HTTP Configuration Details, Outbound, for the format and possible special "shorthand" values you may specify for this parameter, such as *XML, *HTML, *CSV, *PDF and *ZIP.  However, you are not limited to those values – you may explicitly specify an actual content type such as application/zip.

OUTPUT Parameters:

There are no output parameters.