-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
🐞 "/:param" -> "/:param" doesn't return param #405
Comments
Thanks for opening your first issue here! 🎉 Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord |
Hi @pavel1337 , Thanks for creating this issue. Also, do you use Go Modules or
Thank you very much! Additional comment: |
@pavel1337 thank you for your detailed bug report. I can confirm that passing the exact same parameter key including @ReneWerner87, current master branch:
|
Hi guys, thank you for incredibly fast reaction! @Fenny I would not even call it "rare use" it s more like possible "misuse" or even "attack vector". I can confirm that after
with the code as follows:
For me issue is resolved now, even though the current behavior seems somehow incomplete. I would expect |
@ReneWerner87 and I are working on a fix, this happens because of our router logic. It will always check for exact matches first We will change this behaviour to threat |
Fiber version/commit
v1.10.0 (Master branch)
Issue description
Server panics on ":param" GET value if ":param" is set in route. Error is below.
Steps to reproduce
Code snippet
The text was updated successfully, but these errors were encountered: