OptionalmatchOptionalpatchA series of operations to apply to the response body in JSON Patch format (RFC 6902).
Any responses which are received with an invalid JSON body that match this rule will fail.
OptionalreplaceA string or buffer that replaces the response body entirely.
If this is specified, the downstream response will not wait for the original response body, so this may make responses arrive faster than they would be otherwise given large response bodies or slow/streaming servers.
OptionalreplaceThe path to a file, which will be used to replace the response body entirely. The file will be re-read for each response, so the body will always reflect the latest file contents.
If this is specified, the downstream response will not wait for the original response body, so this may make responses arrive faster than they would be otherwise given large response bodies or slow/streaming servers.
OptionalreplaceA headers object which will completely replace the real response headers.
OptionalreplaceA replacement response status code.
OptionalupdateA headers object which will be merged with the real response headers to add or replace values. Headers with undefined values will be removed.
OptionalupdateA JSON object which will be merged with the real response body. Undefined values will be removed, and other values will be merged directly with the target value recursively.
Any responses which are received with an invalid JSON body that match this rule will fail.
Perform a series of string match & replace operations on the response body.
This parameter should be an array of pairs, which will be applied to the body decoded as a string like
body.replace(p1, p2), applied in the order provided. The first parameter can be either a string or RegExp to match, and the second must be a string to insert. The normalstr.replace$ placeholders can be used in the second argument, so that e.g. $1 will insert the 1st matched group.