Quantcast
Channel: Using Optimizely Platforms
Viewing all articles
Browse latest Browse all 8020

Fully qualified URL + EpiServer Content Delivery API

$
0
0

Hello,

I have this issue which I can't figure out what it is:

Based on EpiServer articles I am using a CustomContentModelMapper and overriding below method to get fully qualified urls in Content api resonse.

protected override string ResolveUrl(ContentReference contentLink, string language)
{
string resolvedUrl;
if (_urlResolver == null)
{
resolvedUrl = _urlResolverService.ResolveUrl(contentLink, language);
}
else
{
resolvedUrl = _urlResolver.GetUrl(contentLink, language, new UrlResolverArguments()
{
ContextMode = ContextMode.Default,
ForceCanonical = true
});
}
return string.IsNullOrEmpty(resolvedUrl) ? null : UriSupport.AbsoluteUrlBySettings(resolvedUrl);
}

However for some reason, in my integration enviroment, I see some urls (like image url etc) still coming as reference url and not fully qualified. Pre production and Production environments are working fine as expected.

I am not sure what is it that is causing issue in integration environment. Any thoughts what I could check. Also is there a way to ignore the port number from the fully qualified url.


Viewing all articles
Browse latest Browse all 8020

Trending Articles