You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a field in the response body is prefixed with a path segment from the request, the text after that path segment is not included in the response body.
Expected behavior:
WireMock should evaluate all of the text in the mapping and include all of it in the response.
Request: GET http://{WIREMOCK_SERVER_HOST}/path
Expected response:
{
"field": "pathtext_being_removed_incorrectly"
}
Actual response:
{
"field": "path"
}
Other related info
This issue only occurs when the request path segment is the prefix of a field in the response body. Adding any characters before the request path segment resolves the issue.
Describe the bug
When a field in the response body is prefixed with a path segment from the request, the text after that path segment is not included in the response body.
Expected behavior:
WireMock should evaluate all of the text in the mapping and include all of it in the response.
Test to reproduce
Mapping:
Request:
GET http://{WIREMOCK_SERVER_HOST}/path
Expected response:
Actual response:
Other related info
This issue only occurs when the request path segment is the prefix of a field in the response body. Adding any characters before the request path segment resolves the issue.
Mapping:
Request:
GET http://{WIREMOCK_SERVER_HOST}/path
Response:
The text was updated successfully, but these errors were encountered: