topic Re: Create global request naming rule using configuration API based on SERVICE_REQUEST_ATTRIBUTE in Open Q&A

Create global request naming rule using configuration API based on SERVICE_REQUEST_ATTRIBUTE

henk_stobbe — Tue, 30 Aug 2022 10:37:49 GMT

Hello,

Using the API to create web request naming rules, it it correct that defining ANY placeholder works, but can not be used in the naming rule with the {} format?

Example:

{

"enabled": true,

"namingPattern": "{myplaceholder}",

"conditions": [

{

"attribute": "WEBREQUEST_URL_PATH",

"comparisonInfo": {

"type": "STRING",

"comparison": "BEGINS_WITH",

"value": "/url",

"negate": false,

"caseSensitive": false

}

"Placeholder": [

{"name": "myplaceholder",

"attribute": "WEBREQUEST_URL_PATH",

"kind": "ORIGINAL_TEXT"}

]

}

Gives: 400 Bad request. constraints violation

Pattern contains unknown method naming attribute 'myplaceholder'

KR Henk

Re: Create global request naming rule using configuration API based on SERVICE_REQUEST_ATTRIBUTE

ChadTurner — Sun, 10 May 2020 14:30:09 GMT

Can you try making that rule via the UI? You might get it to work that way.

Re: Create global request naming rule using configuration API based on SERVICE_REQUEST_ATTRIBUTE

curtis_kellogg — Mon, 26 Apr 2021 13:02:42 GMT

The api uses "placeholders" instead of "placeholder" . Change

"Placeholder": [

{"name": "myplaceholder",

"attribute": "WEBREQUEST_URL_PATH",

"kind": "ORIGINAL_TEXT"}

]

"placeholders": [

{"name": "myplaceholder",

"attribute": "WEBREQUEST_URL_PATH",

"kind": "ORIGINAL_TEXT"}

]