Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2022.1

...

REST Client tools created in versions 9.7.x and earlier will be automatically updated to use the new format when you open and save the associated .tst or .pvn
 in pvn in the current version of the product. 

...

The Paths tab lets you configure template parameters for the currently - selected operation.  For For example, a path of "/parabank/services/bank/accounts/{accountId}" has a single path parameter: "accountId".  In In the unconstrained mode, parameters can be fixed, parameterized, or scripted.

...

In the constrained modes, parameters can be set to fixed, parameterized, automatically - generated, or scripted values.

Query Parameters

The Query tab lets you configure the URL query parameters for the currently - selected operation. You can add fixed, parameterized, or scripted values.

In unconstrained mode, parameters can be fixed, parameterized, or scripted.

Image Removed

In the constrained modes, parameters can be set to fixed, parameterized, automatically - generated, or scripted values

Encoding Note

You can opt to append an equals sign (=) to query parameters with empty values. You will only see the equals sign in the URL preview when the parameter is fixed; when it is parameterized or scripted, the equals sign will be added when the test is run. This option is disabled by default.

Image Added

Encoding Note

URL query parameters are formatted according to the URL query parameters are formatted according to the "application/x-www-form-urlencoded" content type. Space characters are replaced with '+'. Non alpha numeric -alphanumeric characters are replaced with a percent sign followed by two hexadecimal digits representing the character code. Names and values are separated by '=' and name-value pairs are separated by '&'. 

...

Virtualize

Internal Transport for Client Tools

Clients chained to responders can route messages to virtual assets on the local server without consuming an HTTP connection by using localhost, 127.0.0.1, or the special host name host.virt.internal. When using localhost or 127.0.0.1, the specified port must match the port Virtualize is deployed on; when using host.virt.internal the port is not used. For example, a virtual asset deployed on http://localhost:9080/myVirtualAsset can also be reached by a chained client using http://host.virt.internal/myVirtualAsset.

Misc Tab

The following options are available in the Misc tab of the REST Client tool:

...