Overview

Use 

Insert excerpt
_http_configuration _http_configuration nopanel true

 to define define settings in a single location and share them between multiple HTTP Action nodes.  

HTTP Configurations work in a similar way to 

Insert excerpt
_styles_ccs_icon _styles_ccs_icon nopanel true

 Shared Styles, where a HTTP Action inherits the settings defined by the associated HTTP Configuration, but these settings can be overridden on the HTTP Action. 

Insert excerpt
_property_tabs _property_tabs name basic-h nopanel true

Basic Settings

Headers

Headers are typically used to specify information for the request, such as the character set being used, session tokens or passwords. Headers can make use of the PhixFlow Secret Key Details see below. For more information see HTTP Header/wiki/spaces//wiki/spaces/HELELP12/p12/pagges/9615615932s/9615615932.    

For example,

• Name: Authorization
• Expression:  ${_datasource.MyAPIKey}

Secret Key Details

Secret Keys allow sensitive data such as passwords or security tokens to be encrypted and stored in the PhixFlow Database.

Secret keys have a name which they can be referenced by using the syntax ${_datasource.keyName}. For full details on secret keys see Secret Key and Local Secret/wiki/spa/wiki/spaces/HEs/HELP12/pP12/pagges/9615611519s/9615611519.

Description

We recommend that you always enter a description to explain the purpose of this item. 

Rate Limiting

Excerpt
name RateLimitingDesc
Rate limiting can be used to limit traffic and help stability.

This

It works by restricting the

amount

number of requests that can be sent

for HTTP Actions that refer to this HTTP Configuration.

.

Excerpt
name RateLimiting
Field  Description

Enable rate limiting

Available when Enable rate limiting is enabled. 

Number

Rate Limiting Toggle on or off to restrict the number of requests.

Requests gained per time period

When enabled the following options are available: Request Capacity Maximum number of requests that can be sent

in

during the

Time period for gaining new requests.Time period for gaining new requests

time period defined by the Request Capacity Rate (ms). Request Capacity Rate (ms)

Available when Enable rate limiting is enabled. 

The

Defines time period, in milliseconds,

for sending requests

in which requests can be processed. The number of requests processed during this period is defined by the Request Capacity and the Maximum Rollover Requests. Maximum

rollover requests

Rollover Requests (Optional)

Available when Enable rate limiting is enabled. 

The maximum number of requests that can be saved, to be sent later. Defaults to to the

requests gained per time period

Request Capacity. Maximum

parallel requests

Parallel Requests (Optional)

Available when Enable rate limiting is enabled. 

The maximum number of requests that can be sent at the same time. Note: If more than the allowed number of requests are

sent

queued, as soon as a request is finished, another is sent. Requests in Queue A read-only field that displays the number of requests waiting to be sent when the properties were opened. Rate Limiting Example

Requests gained per time period: 20

Time period for gaining new requests: 

Request Capacity: 80 Request Capacity Rate: 30000ms Maximum

rollover requests: 25If 10 requests are sent, then 30000ms later another 30 requests are sent, 25 requests would be sent straight away (up to the Maximum rollover request), and the other 5 requests would be sent 30000ms later. 

Rollover Requests:  101 Time Request Capacity Pending Requests Sent Requests Requests Remaining Request Capacity Remaining Maximum Rollover Requests 0s 80 100 80 20 0 0 30s 80 20 20 0 60 60 60s 80+60 0 0 0 140 101 90s 80+101 100 100 0 81 81 120s 80+81 0 0 0 161 101 150s 80+101 150 150 0 31 31 180s 80+31 0 0 0 111 101

Advanced