Overview

Use  HTTP Configuration to share settings between different HTTP Actions. 

HTTP Configurations work in a similar way to  Shared Styles, where if a HTTP Action has a HTTP Configuration set, the settings are inherited from the HTTP Configuration but can be overridden on the HTTP Action. 

 Properties Tab

Basic Settings

Headers

Headers are typically used to specify information for the request, such as character sets, session tokens or passwords. Headers can make use of the Secret Key Details see below. For more information see HTTP Header.    

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.

Description

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

Rate Limiting

Rate limiting can be used to limit traffic and help stability. This works by restricting the amount of requests that can be sent for HTTP Actions that refer to this HTTP Configuration.

Rate Limiting Example

Requests gained per time period: 20

Time period for gaining new requests: 30000ms

Maximum rollover requests: 25

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

Advanced