InboundFile

LANSA Integrator

previous page next page

InboundFile

The InboundFile handler is used to send and receive files.

The HTTP posted content is saved directly to the specified file.

Command	Keyword	Value	Developer notes for Command/Keyword/Value
RECEIVE	HANDLER		InboundFile
	TO	value	Mandatory. File path to receive content.
	APPEND	*YES	Optional. Append content to existing file.
	APPEND	*NO	Default.

Example

RECEIVE HANDLER(InboundFile) TO(/image-upload/photo.jpeg)

When the SEND command of this content handler is executed the following steps occur:

Determine the content-type and read the specified file and send the contents as a HTTP response.

If no CONTENT keyword is present then the Content-Type is determined from the Java Activation Framework FileTypeMap. This is a file extension / MIME type association.

If the HTTP server is an IBM IBM i in MIXED output mode and the content type selected starts with 'text/', the encoding is used to covert the file byte content into Unicode and then converted back to bytes using the value of the CGI-EBCDIC-CCSID property.

If the HTTP server is in BINARY output mode or the content type does not starts with 'text/' then the file contents are sent unaltered.

Syntax:

Command	Keyword	Value	Developer notes for Command/Keyword/Value
SEND	HANDLER		InboundFile
	FILE	value	Mandatory. File path of content.
	UAPATH	value	Optional. User agent save response path.
	UAFILE	value	Optional. User agent save response filename.
	UACACHE	value	Optional. Cache-Control max-age. Default. 0.
	UADISPOSITION	value	Optional. Content-Disposition filename.
	ENCODING		Optional. See ENCODING Used for MIXED mode content encoding.
	CONTENT		Optional. See CONTENT. Content type is obtained from the file type map.
	CHARSET	*YES	Optional. Include charset attribute.
		*NO	Do not include charset attribute.
		*TEXT	Default. Include charset attribute if content is text.

Example

SEND HANDLER(InboundFile) FILE(…)

previous page start next page