From f547624d7e50cef015102dcdc1147cb9357fe9cd Mon Sep 17 00:00:00 2001 From: Stef Heyenrath Date: Sat, 15 Dec 2018 09:20:58 +0100 Subject: [PATCH] Updated Home (markdown) --- Home.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Home.md b/Home.md index 69d5b4f..2719eab 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 predefined HTTP responses for requests matching criteria, [Stubbing](https://github.com/StefH/WireMock.Net/wiki/Stubbing) & [Request Matching](https://github.com/WireMock-Net/WireMock.Net/wiki/Request-Matching); +A core feature of WireMock is the ability to return predefined HTTP responses for requests matching criteria, [Stubbing](https://github.com/StefH/WireMock.Net/wiki/Stubbing) & [Request Matching](https://github.com/WireMock-Net/WireMock.Net/wiki/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.