From c33ed81e5bb907d4650bf3933b99cede92df8542 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E4=BA=8E=E7=8E=89=E6=A1=94?= Date: Fri, 20 Sep 2019 18:45:24 +0800 Subject: [PATCH] doc: update UrlCleaner description in sentinel-web-servlet README.md (#1051) --- sentinel-adapter/sentinel-web-servlet/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sentinel-adapter/sentinel-web-servlet/README.md b/sentinel-adapter/sentinel-web-servlet/README.md index fbb0227c..40bc2e65 100755 --- a/sentinel-adapter/sentinel-web-servlet/README.md +++ b/sentinel-adapter/sentinel-web-servlet/README.md @@ -55,8 +55,8 @@ For REST APIs, you have to clean the URL resource (e.g. `/foo/1` and `/foo/2` -> the amount of context and resources will exceed the threshold. If you need to exclude some URLs (that should not be recorded as Sentinel resources), you could also -leverage the `UrlCleaner` interface. You may unify the unwanted URLs to the empty string `""`, +leverage the `UrlCleaner` interface. You may unify the unwanted URLs to the empty string `""` or `null`, then the URLs will be excluded (since Sentinel 1.6.3). `RequestOriginParser` interface is useful for extracting request origin (e.g. IP or appName from HTTP Header) -from HTTP request. You can implement your own `RequestOriginParser` and register to `WebCallbackManager`. \ No newline at end of file +from HTTP request. You can implement your own `RequestOriginParser` and register to `WebCallbackManager`.