alibaba / alibaba/Sentinel

Sentinel集成springcloud gateway时,被限流后为什么还会继续调用我定义的GlobalFilter?

Open
#2,491 4 comments 0 reactions 0 assignees View on GitHub
kind/question
Dominant language
Java
Stars
23.1k
Forks
8.1k
PR merge metrics
No merged PRs in 30d

Description

在做测试时,发现,即使请求被限流了,程序还是会调用我定义的GlobalFilter,比如权限判断的GlobalFilter,请求日志的GlobalFilter,
![image](https://user-images.githubusercontent.com/17404637/145991145-c5ab0723-5b09-47b2-8ae7-7a95183d331e.png)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the interaction between Sentinel rate limiting, Spring Cloud Gateway, and the user-defined GlobalFilter instances for permission checks and request logging. Inspect the integration and filter execution order to determine why rate-limited requests still reach those filters. Done means a confirmed explanation of the ordering and a clear expected behavior for rejected requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.