-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 with pathParam returning 400 code #2439
Comments
We have this issue as well, it seems to only occur when the pathParam is the last element of the url. |
On my Mac, Bruno 1.19.0 works fine, with a path param at the end of a url. |
Same here. We're always getting HTTP 400 as response. |
This is working endpoint, just checked, gave same results, as described in a bug.
Getting same, when this is not at end of the url, like {baseUrl}/:id/status. |
Could you share more information by sharing a .bru file or a JSON export? |
Attached collection: |
@sanjai0py I made some test locally, and my fix would work. I suppose that the problem is wider, "params" property is the same as axios, and - I suppose - they are in conflict. But since we already translate variables, we can simply empty it. |
PR has been merged. This is set to be released in the upcoming |
@helloanoop Any info on when that release might happen? Thanks! |
I have checked the following:
Describe the bug
When using :pathParam in request, then getting response code 400. Same with hardcoded parameter giving correct response.
In attachment you will find two same requests, one with pathParam (returns 400), second without (returns 200 and correct data). And two screenshots of same requests.
.bru file to reproduce the bug
Not working:
meta {
name: Get user with pathParam
type: http
seq: 2
}
get {
url: https://spring-boot-test-aplication.herokuapp.com/api/users/findById/:id
body: none
auth: none
}
params:path {
id: 16
}
Same but without pathParam and working:
meta {
name: Get user without pathParam
type: http
seq: 3
}
get {
url: https://spring-boot-test-aplication.herokuapp.com/api/users/findById/16
body: none
auth: none
}
Screenshots/Live demo link
The text was updated successfully, but these errors were encountered: