5.4.1 SERVICE_LOAD
If the HTTPService is being used for inbound services, then the SERVICE_LOAD keywords will contain a selection of the HTTP protocol properties sent by the remote HTTP client program.
For a complete list of HTTP protocol property names refer to the SERVICE_LOAD command.
Syntax:
|
Command |
Keyword |
Value |
Developer notes for Command/Keyword/Value |
|
SERVICE_LOAD |
BIND |
|
Optional. See BIND. |
|
ARCHIVE |
|
Optional. See ARCHIVE. |
|
|
ENCODING |
|
Optional. See ENCODING. |
|
|
*BINARY |
Archive content with no encoding changes. |
||
|
SCHEMA |
|
Optional. See SCHEMA. |
|
|
VALIDATING |
|
Optional. See VALIDATING. |
|
|
DOMSET |
|
Optional. See DOMSET. |
|
|
DOMSETMODEL |
|
Optional. See DOMSETMODEL. |
|
|
DOMSETRESULT |
|
Optional. See DOMSETRESULT. |
If the ARCHIVE keyword is used the service will use the ENCODING keyword value if it is present or determine the encoding from the protocol content-type entry or use a default value to convert the received byte content to a Unicode string ready for the archiving stage.
The ENCODING keyword is only used when the service is going to archive the received content. The keyword value of *BINARY instructs the service to write the byte content unaltered to the archive file.
The ARCENCODE keyword controls the archive file content encoding.
If the content type is not of type text or XML then the byte content is written to the file unaltered. So posted images and PDF document and other non-text type content will be archive unaltered.
Using the keyword ENCODING (*BINARY) with the ARCHIVE keyword causes all received content to be archived unaltered.