aa4ee27d4a
When there is a fallback in webflux (like a hystrix fallback or a webflux fallback method that involves visiting a new URL). This interceptor would be invoked twice, one for origin request and another for fallback request. The ServerWebExchange for these two aren't exactly the same one, but the former one is a delegate inside of the latter one, thus, they share the same attributes. The problem of the old code is that get the span from attributes within the execution of Mono would get span for the latter request twice. so just move this part of code out could solve the problem. It seems impossible to make the mono chain work like expected. So add a check about whether the best matching pattern really matches the URL. This check code is how webflux generating the best match pattern, |
||
|---|---|---|
| .. | ||
| customize-enhance-plugin | ||
| ehcache-2.x-plugin | ||
| gson-2.8.x-plugin | ||
| guava-cache-plugin | ||
| kotlin-coroutine-plugin | ||
| mybatis-3.x-plugin | ||
| optional-spring-plugins | ||
| quartz-scheduler-2.x-plugin | ||
| sentinel-1.x-plugin | ||
| trace-ignore-plugin | ||
| zookeeper-3.4.x-plugin | ||
| pom.xml | ||