This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 5%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
Setting up an Azure API Operation, the URL in the setting is "/SomeName"
This value seems to concatenate onto the Backend-service Base-URL
Example: If Backend-Service Base Urls is https://someurl.com/test
The backend url with the above URL in the setting ends up as:
https://someurl.com/test/SomeName
It does not appear I can set the back end to connect to https://someurl.com/test/someothername
Is there a way to circumvent this behavior?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 59%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
@Robert Heynen Thanks for reaching out. In APIM, the Backend URL can inherit the APIM URL if the Backend-service Base-URL is not specified or is left blank.
To change the behavior of the Backend URL concatenation in APIM, you can specify a Backend-service Base-URL for your API. This will ensure that the APIM service forwards requests to the specified backend URL.
or you can modify this behavior using policies in APIM. For instance, you can use the set-backend-service policy to direct an incoming API request to a backend.
<policies>
<inbound>
<base />
<set-backend-service base-url="https://someotherurl.com" />
</inbound>
<backend>
<base />
</backend>
<outbound>
<base />
</outbound>
<on-error>
<base />
</on-error>
</policies>
https://learn.microsoft.com/en-us/azure/api-management/backends?tabs=bicep
https://learn.microsoft.com/en-us/azure/api-management/set-backend-service-policy
You can modify the policy to suit your specific needs.
I hope this helps! Let me know if you have any further questions.
I specified the back-end URL and it still happens.
Method Setting like this:
Setting like this (it is dynamic so I use a variable above to define which environment)
API URL when I test automatically concatenates /addItems after /RequirementManagement/Requirement
Even when I hard code the base URL, this happens.
@Robert Heynen Following up on my previous comment to check if you are able to resolve the issue with rewrite-uri policy as mentioned above. Please let me know if you have any further queries
This worked perfectly - thank you!
@Robert Heynen Thanks for your response. Glad to know that it helped. I have converted my comment to answer. Feel free to 'Accept as Answer' so it can help other community members facing the similar issue.
@Robert Heynen Thanks for getting back, this behavior is by design. you can use the rewrite policy at the operation level, the "template" value will be the value you want to append to the backend base url
<rewrite-uri template="/" />
please try this and let me know incase of further queries, I would be happy to assist you.