Request URL not build properly

Bug Report
1

since I updated from 7.15. to 7.19 I can not run any request anymore as my URLs are not build properly from service, path-param and endpoint param: see image.
As we see this on more than one machine, I would assume it is a systematic problem.

and how can I downgrade? I can not find older versions for download…

APIDOG_error-2025-06-30_14_14_07.png
APIDOG_error-2025-06-30_14_14_07.png1916×1037 156 KB

2

Could you try using the path starting with / as normal, or directly use {{RaiSuPath}} instead of {RaiSuPath}?

3

changing to a path starting with / (and removing the slash from the variable) it does work again. but is this intended? it will create a lot of work for us to change all the definitions. and it creates a risk, if variable is not defined in some environments we get // which does not work for our server.

Edit: using the variable directly (with slash in variable) doesn’t work. obviously variables starting with a slash are a problem now…

grafik.png
grafik.png1163×772 76.5 KB

4

Here are the download links for the previous version:

We have investigated the issue, and it appears unrelated to the application version. The problem is likely caused by an path variables syntax without leading slash. If you want to use variables diirectly in URL, the correct format requires double curly braces, {{RaiSuPath}}. Using single braces, {RaiSuPath}, will not work as expected.
4. Save the changes and import the modified .apidog.json file back into Apidog.

5

If you need to update these variables in bulk, you can do so by following these steps:

  1. Export your project in the Apidog format, which will generate a .apidog.json file. Backup the file before changing it.
  2. Open this file in an IDE or a text editor.
  3. Use the “Find and Replace” feature to replace all occurrences of {RaiSuPath} with {{RaiSuPath}}.
6

thank you for the download links.
I can confirm, that it works with 7.15. so something changed in 7.18 or 7.19 which prohibits the usage of a path parameter with leaading slash.
(it was not intended to be directly a variable in the url definition, although named similar)

7

Could you share some screenshots or logs about the working example at your end when using 2.7.15?

8

Hi, please update to version 2.7.20 and try again, this version includes the relevant optimizations.

9

thank you. I can confirm, it works again. But as far as I see, this fix is not mentioned in the changelog. Why not?