-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
request help: url contains Chinese, will decode utf8 encoded url into hexadecimal format of \x #7838
Comments
I test with the above test case, and both successfully match the route. |
Em... Match route is ok. I want to say , when url contains Chinese ,upstream will recevie hex ,like this |
#7401 |
I set |
request APISIX
upstream nginx log:
APISIX will not change your URL, it just forward your URL if you don't use any plugin. So where is the problem? Many web server, like nginx, it will decode the url-encoded URL before match the route. So I guess you could encoded your URL twice like the example above. |
@biubiue any updates? If not, please close this issue. Thanks. |
Due to lack of the reporter's response this issue has been labeled with "no response". It will be close in 3 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions. |
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time. |
Current Behavior
raw url: https://xxx.com/a/中文.html
url will encode this: https://xxx.com/a/%E4%B8%AD%E6%96%87.html
fact in apisix: https://xxx.com/a/\xE4\xB8\xAD\xE6\x96\x87.html
Expected Behavior
No response
Error Logs
No response
Steps to Reproduce
raw url: https://xxx.com/a/中文.html
url will encode this: https://xxx.com/a/%E4%B8%AD%E6%96%87.html
fact in apisix: https://xxx.com/a/\xE4\xB8\xAD\xE6\x96\x87.html
Environment
apisix version
):2.15uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: