-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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]: !!!!123.60.95.134 redirect attack #2350
Labels
bug
Something isn't working
Comments
f1ad778 Never upload any sensitive file when developing your application |
There really needs to be a more rigorous code review. |
cyhasuka
added a commit
to cyhasuka/ragflow
that referenced
this issue
Sep 10, 2024
cike8899
added a commit
to cike8899/ragflow
that referenced
this issue
Sep 10, 2024
1 task
JinHai-CN
pushed a commit
that referenced
this issue
Sep 10, 2024
Already fixed, thanks for the reminder. |
cike8899
added a commit
to cike8899/ragflow
that referenced
this issue
Sep 11, 2024
6 tasks
KevinHuSh
pushed a commit
that referenced
this issue
Sep 11, 2024
Halfknow
pushed a commit
to Halfknow/ragflow
that referenced
this issue
Nov 11, 2024
### What problem does this PR solve? fix: 123.60.95.134 redirect attack infiniflow#2350 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
Halfknow
pushed a commit
to Halfknow/ragflow
that referenced
this issue
Nov 11, 2024
infiniflow#2366) ### What problem does this PR solve? feat: Proxy the api address to the local nginx address infiniflow#2350 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for the same bug?
Branch name
main
Commit ID
lastest
Other environment information
No response
Actual behavior
somebody replaces the backend to his own server!!! 123.60.95.134 instead of the localhost
Expected behavior
No response
Steps to reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: