From f6f63c1fd99d262fbf770720ac6a84bb2498e6ee Mon Sep 17 00:00:00 2001 From: Stef Heyenrath Date: Tue, 16 Oct 2018 18:44:41 +0200 Subject: [PATCH] Updated Home (markdown) --- Home.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Home.md b/Home.md index 96958e0..114c743 100644 --- a/Home.md +++ b/Home.md @@ -1,7 +1,7 @@ # Welcome to the WireMock.Net wiki ## Stubbing & Request Matching -A core feature of WireMock is the ability to return canned HTTP responses for requests matching criteria, see [Wiki : Stubbing & Request Matching](https://github.com/StefH/WireMock.Net/wiki/Stubbing-and-Request-Matching). +A core feature of WireMock is the ability to return predefined HTTP responses for requests matching criteria, see [Wiki : Stubbing & Request Matching](https://github.com/StefH/WireMock.Net/wiki/Stubbing-and-Request-Matching). ## Proxying WireMock.Net has the ability to selectively proxy requests through to other hosts. This supports a proxy/intercept setup where requests are by default proxied to another (possibly real, live) service, but where specific stubs are configured these are returned in place of the remote service’s response. Responses that the live service can’t be forced to generate on demand can thus be injected for testing.