/AWS1/CL_APMHTTPROUTEMATCH¶
An object that represents the requirements for a route to match HTTP requests for a virtual router.
CONSTRUCTOR
¶
IMPORTING¶
Optional arguments:¶
iv_prefix
TYPE /AWS1/APMSTRING
/AWS1/APMSTRING
¶
Specifies the path to match requests with. This parameter must always start with
/
, which by itself matches all requests to the virtual service name. You can also match for path-based routing of requests. For example, if your virtual service name ismy-service.local
and you want the route to match requests tomy-service.local/metrics
, your prefix should be/metrics
.
io_path
TYPE REF TO /AWS1/CL_APMHTTPPATHMATCH
/AWS1/CL_APMHTTPPATHMATCH
¶
The client request path to match on.
it_queryparameters
TYPE /AWS1/CL_APMHTTPQUERYPARAMETER=>TT_HTTPQUERYPARAMETERS
TT_HTTPQUERYPARAMETERS
¶
The client request query parameters to match on.
iv_method
TYPE /AWS1/APMHTTPMETHOD
/AWS1/APMHTTPMETHOD
¶
The client request method to match on. Specify only one.
iv_scheme
TYPE /AWS1/APMHTTPSCHEME
/AWS1/APMHTTPSCHEME
¶
The client request scheme to match on. Specify only one. Applicable only for HTTP2 routes.
it_headers
TYPE /AWS1/CL_APMHTTPROUTEHEADER=>TT_HTTPROUTEHEADERS
TT_HTTPROUTEHEADERS
¶
The client request headers to match on.
iv_port
TYPE /AWS1/APMLISTENERPORT
/AWS1/APMLISTENERPORT
¶
The port number to match on.
Queryable Attributes¶
prefix¶
Specifies the path to match requests with. This parameter must always start with
/
, which by itself matches all requests to the virtual service name. You can also match for path-based routing of requests. For example, if your virtual service name ismy-service.local
and you want the route to match requests tomy-service.local/metrics
, your prefix should be/metrics
.
Accessible with the following methods¶
Method | Description |
---|---|
GET_PREFIX() |
Getter for PREFIX, with configurable default |
ASK_PREFIX() |
Getter for PREFIX w/ exceptions if field has no value |
HAS_PREFIX() |
Determine if PREFIX has a value |
path¶
The client request path to match on.
Accessible with the following methods¶
Method | Description |
---|---|
GET_PATH() |
Getter for PATH |
queryParameters¶
The client request query parameters to match on.
Accessible with the following methods¶
Method | Description |
---|---|
GET_QUERYPARAMETERS() |
Getter for QUERYPARAMETERS, with configurable default |
ASK_QUERYPARAMETERS() |
Getter for QUERYPARAMETERS w/ exceptions if field has no val |
HAS_QUERYPARAMETERS() |
Determine if QUERYPARAMETERS has a value |
method¶
The client request method to match on. Specify only one.
Accessible with the following methods¶
Method | Description |
---|---|
GET_METHOD() |
Getter for METHOD, with configurable default |
ASK_METHOD() |
Getter for METHOD w/ exceptions if field has no value |
HAS_METHOD() |
Determine if METHOD has a value |
scheme¶
The client request scheme to match on. Specify only one. Applicable only for HTTP2 routes.
Accessible with the following methods¶
Method | Description |
---|---|
GET_SCHEME() |
Getter for SCHEME, with configurable default |
ASK_SCHEME() |
Getter for SCHEME w/ exceptions if field has no value |
HAS_SCHEME() |
Determine if SCHEME has a value |
headers¶
The client request headers to match on.
Accessible with the following methods¶
Method | Description |
---|---|
GET_HEADERS() |
Getter for HEADERS, with configurable default |
ASK_HEADERS() |
Getter for HEADERS w/ exceptions if field has no value |
HAS_HEADERS() |
Determine if HEADERS has a value |
port¶
The port number to match on.
Accessible with the following methods¶
Method | Description |
---|---|
GET_PORT() |
Getter for PORT, with configurable default |
ASK_PORT() |
Getter for PORT w/ exceptions if field has no value |
HAS_PORT() |
Determine if PORT has a value |