Forum Discussion
SiKing
12 years agoCommunity Expert
This is starting to get outside my area of expertise.
We have two resources: one is at "/{gameCode}/issues/current", and the other is at "/{gameCode}/issues/{issueId:[0-9]+}". The way the backend distinguishes between two URLs, is that the second allows only numbers (the stuff after the colon is a regex).
SoapUI does not throw any kind of an error when making the call. It simply cannot find the parameter, regardless if I call it "issueId:[0-9]+" or "issueId".
One of our developers is working with the Swagger guys, and he fixed it right in the code. I do not know the ticket number, and the developer is currently on vacation. I will try to track this down for you.
We have two resources: one is at "/{gameCode}/issues/current", and the other is at "/{gameCode}/issues/{issueId:[0-9]+}". The way the backend distinguishes between two URLs, is that the second allows only numbers (the stuff after the colon is a regex).
SoapUI does not throw any kind of an error when making the call. It simply cannot find the parameter, regardless if I call it "issueId:[0-9]+" or "issueId".
One of our developers is working with the Swagger guys, and he fixed it right in the code. I do not know the ticket number, and the developer is currently on vacation. I will try to track this down for you.
Related Content
- 10 months ago
- 5 years ago
Recent Discussions
- 5 days ago
- 10 days ago