HTTP/2 UDRs

HTTP/2 UDRs

The HTTP/2 UDR types are designed to exchange data between the workflows, and can be viewed in the UDR Internal Format Browser.

The supported HTTP/2 UDRs are as follows:

Push

The Push UDR can be used for sending additional resources belonging to a request.

The following fields are included in the Push UDR:

Field

Description

Field

Description

path (string)

Set the URI path to be used for the push.

request (RequestCycle (http))

The RequestCycle UDR the Push UDR belongs to.

Cookie

The Cookie UDR is used for including cookie information in Response UDRs.
 The following fields are included in the Cookie UDR:

Field

Description

Field

Description

domain (string)

The domain to which the cookie belongs.

expires (string)

The date and time when the cookie expires.

httponly (boolean)

If set to true, cookies will not be exposed through channels other than HTTP and HTTPS requests.

name (string)

The name of the cookie.

path (string)

The path to the page the cookie belongs to, for example "mydomain.com/mypage.html".

secure (boolean)

Indicates whether the data is sent in secure mode or not.

value (string)

The value of the cookie.

Response

The Response  UDR contains the response to the request and is incorporated in the RequestCycle UDR.

The following fields are included in the Response UDR:

Field

Description

Field

Description

body (any)

This field contains the message body, that is, the payload, of the response. For HEAD requests, a body is never present in the response. For all other request methods, responses are present with the following exceptions:

  • responses to CONNECT requests with status code 2xx

  • responses to requests with status code 1xx (informational)

  • responses to requests with status code 204 (no content)

  • responses to requests with status code 304 (not modified)

cookies (list<CookieUDR>)

This field contains any Cookie UDRs included.

headers (map<string,list<string>>)

This field is populated by all the headers present in the response. The map keys contain header field names and the content is stored in the corresponding map values.

httpVersion (string)

This field contains the HTTP version; HTTP/1 or HTTP/2.

mimetype (string)

The type of the content, for example "text/html", "image/gif", etc.

openAPIUDR (DRUDR)

This field is used if an OpenAPI profile has been associated with the HTTP/2 Server agent.

statusCode (int)

The HTTP status code, for example: 200 - OK, 404 - Not Found, etc.

MultipartSegment

The MultipartSegment UDR is used when sending requests containing multiple types of content, or when the content has been split up in multiple parts.
 The following fields are included in the MultipartSegment UDR:

Field

Description

Field

Description

content (bytearray)

The body of the message.

contentType (string)

The type of the content, for example "multipart/form-data", "multipart/mixed", etc.

filename (string)

The actual file name, for example "img.jpg".

name (string)

An informal name of the file, for example "myFile".