-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
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
[BUG] fallbackUri issue #5494
Labels
type: bug
Something isn't working
Comments
RayayChung
pushed a commit
to RayayChung/shenyu
that referenced
this issue
Mar 16, 2024
RayayChung
pushed a commit
to RayayChung/shenyu
that referenced
this issue
Mar 16, 2024
RayayChung
pushed a commit
to RayayChung/shenyu
that referenced
this issue
Mar 16, 2024
RayayChung
pushed a commit
to RayayChung/shenyu
that referenced
this issue
Mar 16, 2024
* avoid redirect loop * add unit test
RayayChung
pushed a commit
to RayayChung/shenyu
that referenced
this issue
Mar 20, 2024
moremind
added a commit
that referenced
this issue
Mar 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
fallback config:
when fallback is triggered, the
ip:port
info is missing from the fallback request.From the current code, it appears that this
fallbackUri
field supports two configuration methods(eg.fallback:/far/boo
orhttp://ip:port/far/boo
). Does this align with our expectations?Expected Behavior
No response
Steps To Reproduce
No response
Environment
Debug logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: