The HTTP/2 Server agent enables you to configure an HTTP server in a real-time workflow. The agent receives requests, converts them into UDRs routed into the workflow, and then sends responses back over a TCP/IP connection.
The agent can be used for both HTTP/1 and HTTP/2.
Prerequisites
The reader of this information should be familiar with:
Hypertext Transfer Protocol version 2 (RFC 7540: https://tools.ietf.org/html/rfc7540)
Hypertext Transfer Protocol version 1.1 (RFC 2616: http://www.ietf.org/rfc/rfc2616.txt)
- The Transport Layer Security (TLS) Protocol version 1.2 (RFC 5246: https://www.ietf.org/rfc/rfc5246.txt)
Configuration
The HTTP/2 agent's configuration contains four tabs; Server, Overload Protection, OpenAPI/5G and Authentication.
Server
The Server tab contains the following settings:
...
Use SSL
...
Select this option if you want to use SSL.
...
Enter the port number you want the agent to bind to.
...
Client Timeout (sec)
...
The period in seconds after which the HTTP/2 Server should close the connection if a client is inactive. That is, this is the period of inactivity from when the client has opened the connection or received the last expected response until the server should close the connection. For example, if Client Timeout is set to 6, this means that the server will close the connection if the client is inactive for 6 seconds.
...
Select the character set you want to use as default character set. UTF-8 is preselected.
This character set is used if the character set requested by Accept-Charset is not found in system.
...
If gzip is requested, then the response is gzipped with the compression level you specify in this field, 1-9.
Overload Protection
The Overload Protection tab controls overload protection and contains the following settings:
...
Enable Overload Protection
...
Select this option if you want enable overload protection.
...
OpeAPI/5G
The OpenAPI/5G tab contains the following settings:
...
Use OpenAPI Profile
...
Select this option if you want the agent to use an OpenAPI profile.
...
Select this option if you want to validate the OpenAPI profile.
| Note | ||
|---|---|---|
| ||
Turning this option ON will have a very significant performance impact on the overall performance of the flow. When validation is enabled, each payload will be validated against the Open API schema, an operation that can be very resource-intensive. We recommend to only enable this setting during development and testing and to disable it in a stable production environment. |
...
Authentication
The Authentication tab contains the following settings:
...
Use Token Authentication
...
Select this option if you want to use token authentication.
...
Access Token Required
...
If you have selected Token Authentication, you can select this option if you want the access token to be required.
...
Public Key
...
Paste the public key into this field.
Input/Output Data
Input Data
9.40.4.1 NRFSpecificationUDRwill only be required when Custom Specification is enabled on the 5G Profile. Refer to 5G Profile or more information about enabling Custom Specifications for 5G.
Output Data
...
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
This section contains the following subsections: |