Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have just completed my first End-2-End testing in SDL Web 8 where I have created, published (through topology manager) and displayed a piece of content in a .NET Web Application. This feels like a major milestone.

To test some of the functionality I tried loading various items like page content and dynamic links using the new .NET RESTful API.

One of my test cases is resolving a component link with the following test code.

ComponentLink compLink = new ComponentLink(777);
Link myCompLink = compLink.GetLink(12, 124704,8, "targert='wow'", "My text", true, true);

The link resolves correctly, and the resulting URL property contains something like "". I was very suprised to see an absolute URL here.

I recognize the domain from when I set up a Website with Topology Manager, and the 'myfirstwebapp' from the WebApplication I set up with Topology Manager. In many cases this makes sense. However in our case we have multiple sites and apps consuming this content, and as such need to leverage relative URLs.

When I look in the LINK_INFO table of the Broker Database I see the URLs I would like to use.

Is there a way to configure the micro services to return relative URLs rather than absolute ones?

share|improve this question
up vote 8 down vote accepted

Yes, there is. In the cd_link_conf.xml of the (Session-enabled) Content Service there is a OverrideDiscoveryService attribute. If you set that to true, the Content Service will switch back to old-style link resolving using the mappings defined in cd_link_conf.xml and if you don't define any mappings in there, you will get relative URLs.

Unfortunately, the implementation of this setting is defective; after a while it will revert to using the Discovery Service (and absolute links) anyways. This defect is fixed in the upcoming 8.1.1 release.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.