We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
我在sentinel-dashboard配置了一个接口的热点规则但是没有生效,于是我就进行了DEBUG调试 我发现当一个接口被请求之后,首先进入的是一个SentinelWebInterceptor SentinelWebInterceptor继承AbstractSentinelInterceptor抽象类,preHandle方法被调用 在这个方法中会调用SphU.entry方法 Entry entry = SphU.entry(resourceName, ResourceTypeConstants.COMMON_WEB, EntryType.IN); 但是SphU.entry没有传递当前接口请求的参数
在SphU.entry方法内部它传递的是一个默认常量OBJECTS0(对象数组,长度为0)
最终导致在ParamFlowSlot类中方法entry被调用的时候args是一个长度为0的对象数组
在ParamFlowChecker类中方法passCheck始终true
上面是我调试的结果
The text was updated successfully, but these errors were encountered:
sentinel版本1.8.6
Sorry, something went wrong.
No branches or pull requests
我在sentinel-dashboard配置了一个接口的热点规则但是没有生效,于是我就进行了DEBUG调试
我发现当一个接口被请求之后,首先进入的是一个SentinelWebInterceptor
SentinelWebInterceptor继承AbstractSentinelInterceptor抽象类,preHandle方法被调用
在这个方法中会调用SphU.entry方法
Entry entry = SphU.entry(resourceName, ResourceTypeConstants.COMMON_WEB, EntryType.IN);
但是SphU.entry没有传递当前接口请求的参数
在SphU.entry方法内部它传递的是一个默认常量OBJECTS0(对象数组,长度为0)
最终导致在ParamFlowSlot类中方法entry被调用的时候args是一个长度为0的对象数组
在ParamFlowChecker类中方法passCheck始终true
上面是我调试的结果
The text was updated successfully, but these errors were encountered: