Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Walkthrough스프링 클라우드 게이트웨이 설정에서 Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@src/main/resources/application.yml`:
- Around line 51-60: 현재 Path predicate에서 "!/v1/images/upload" 부정 패턴이 동작하지 않으므로
업로드를 제외하려면 라우트를 두 개로 분리하세요: 먼저 공개 라우트(id: image-public)로 Path predicate에
"/v1/images/upload"만 매칭되게 하고 filters에서 AuthenticationFilter를 제거하여 인증 없이 통과시키고, 그
다음에 기존의 보호된 라우트(id: image-private)를 두어 Path predicate에 "/v1/images/**"를 매칭시키고
filters에 AuthenticationFilter를 적용하세요; 라우트 순서(image-public 먼저, image-private 다음)를
보장하면 "/v1/images/upload"는 공개 라우트가 처리되고 나머지 경로는 인증 라우트로 처리됩니다.
Summary by CodeRabbit
릴리스 노트