HTTP trigger

Operation name

Functional Overview

Fire image

Properties

HTTP trigger settings

Execution content settings

Execution option settings

Trigger Variables

How to set request parameters

How to set multiple part form data

<form method="post" action="<HTTP trigger URL>" enctype="multipart/form-data">
<p>First name<br>
<input type="text" name="firstname"></p>
<p>Last name<br>
<input type="text" name="lastname"></p>
<p>Profile picture<br>
<input type="file" name="attachment"></p>
<p><input type="submit" value="Send"></p>
</form>

Content-Type: multipart/form-data; boundary=<boundary>

--<boundary>
Content-Disposition: form-data; name="firstname"

Ichiro

--<boundary>
Content-Disposition: form-data; name="lastname"

Suzuki

--<boundary>
Content-Disposition: form-data; name="attachment"; filename="profile.jpg"
Content-Type: image/jpeg

</data/profile.jpg data>

--<boundary>--

• Parameter name distinguishes between upper and lower case.
• Cannot treat parameter name of 2 byte character.
• If parameter with same name exists, stores the value of the first detected parameter to script variable.
• If parameter value is treated as character string, encoding will be performed with [Request setting/Encoding].
  However, if charset parameter exists in Content-Type header of parameter, encoded with charset parameter value.

CSV Output

• If the data is XML representation of an table model type data, it is converted into CSV data.
  • The record of CSV is delimited by ',' comma.
  • The character used as delimiter, double quotes, or newline characters found in the record are escaped by a double quotes.
  • The literal representation of " used in records will be escaped by double prepending it an another double quote.
• If the data dereferenced is not an XML, the string representation of the data is output.

JSON Output

• If XML format data that follows the rule of "Converting JSON Format Data" is given, outputs by converting into JSON format data.
• If data other than the above ones is given, outputs the data character string expression.

File Output

Converting JSON Format Data

<-- If root is JSON object of object type -->
<?xml version="1.0"?>
<root type="object">
  <JSON member name type="Attribute value that shows JSON type">value</JSON member name>
    :
</root>

<-- If root is JSON object of array type -->
<?xml version="1.0"?>
<root type="array">
  <element type="Attribute value that shows JSON type">value</element>
    :
</root>

<-- If JSON member name is false as XML element name -->
<?xml version="1.0"?>
<root type="object">
  <member type="Attribute value that shows JSON type" name="JSON member name">value</member>
    :
</root>

{"name":"Suzuki"}

<root type="object">
  <name type="string">Suzuki</name>
</root>

["apple","grape","orange"]

<root type="array">
  <element type="string">apple</element>
  <element type="string">grape</element>
  <element type="string">orange</element>
</root>

{"name":"Suzuki"}

<name type="string">Suzuki</name>

{"age":37}

<age type="number">37</age>

{"success":true}

<success type="boolean">true</success>

{"name":{"first":"Ichiro","last":Suzuki"}}

<name type="object">
  <first type="string">Ichiro</first>
  <last type="string">Suzuki</last>
</name>

<JSON member name type="array">
  <element type="Attribute value showing JSON type">value</element>
    :
</JSON member name>

{"fruits":["apple","grape","orange"]}

<fruits type="array">
  <element type="string">apple</element>
  <element type="string">grape</element>
  <element type="string">orange</element>
</fruits>

{"name":null}

<name type="null"/>

{"1name":"Suzuki"}

<member type="string" name="1name">Suzuki</member>

Response status code

• If the trigger variable "trigger.status_code" is not set, or data other than the above is received, response status code will be decided as follows.
  • "200" if the script executed with HTTP trigger ended successfully.
  • "500" if the script executed with HTTP trigger ended abnormally.
• If error occurred during request analysis before script execution, response status will be "400".


• If the trigger of specified URL is invalid, response status code will be "403".


• If the trigger of specified URL is not found, response status code will be "404".


• After the script execution, if error occurred before returning response, response status code will be "500".


• If [Return page generated by script] is selected in [Action when executed successfully], and "204" or "304" is set in the trigger variable "trigger.status_code", response body will be empty despite returning of page generated by the script.


• If [Return error page of web server] is selected in [Action when exit abnormally], and the script executed with HTTP trigger abnormally ended, status code will be "500" regardless of the status code specified in the trigger variable "trigger.status_code".

Log Output

Specification limit

• You cannot manage HTTP session.


• If [Enable HTTPS] in [Control Panel] - [DataSpiderServer Settings] - [Security] tab is checked, HTTP access will be redirected to HTTPS port.


• If data returned as response is XML data, XML data encoding declaration will be the encoding specified by [Response settings/Encoding].


• If the data to return as response is JSON data, encoded as UTF-8.

Main exceptions

Notes

• After registering trigger, if you change the status of the services and scripts that are set to trigger (or add/delete script variables, change service name/script name), those changes are not reflected in the registered trigger.
  Open the properties of the target trigger, after re-selection of services and scripts Click [Finish] to re-register.


• Depending on Browser settings, If you do not clear cache, the process result may not be displayed normally.
  In such cases, please go to reload the browser.