浏览代码

doc: update UrlCleaner description in sentinel-web-servlet README.md (#1051)

master
于玉桔 Eric Zhao 5 年前
父节点
当前提交
c33ed81e5b
共有 1 个文件被更改,包括 2 次插入2 次删除
  1. +2
    -2
      sentinel-adapter/sentinel-web-servlet/README.md

+ 2
- 2
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. 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 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). 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) `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`.
from HTTP request. You can implement your own `RequestOriginParser` and register to `WebCallbackManager`.

正在加载...
取消
保存