Due to recent issues with the .ws, domain name system, a preventative improvement is planned to be released on Wednesday the 10th of February to transition Dynamic Content images to loading from a .net domain.
• Dynamic Content
• Content Authoring
During this window, a transparent change will take effect in the following content delivery APIs:
The content delivery APIs return JSON/HTML that is used to render content on websites and apps. The API response can include a reference to images including where to load them from, for example:
Client applications use this information to construct the image URLs to display to end users.
The planned release will update API responses to transition “defaultHost” from a .ws domain to an equivalent .net domain (classic.cdn.media.amplience.net & cdn.media.amplience.net).
The equivalent .net domain will have all the same functionality and characteristics including the exact same SSL cipher suite and features to ensure compatibility with the exact same set of browsers.
Who is impacted
• The change will only impact customers using the Dynamic Content product. Customers using the Dynamic Media product only will be unaffected as the hostname used to load media is defined by your code.
• This change will not impact customers who use a custom domain name (e.g. images.mybrand.com) and the API will continue to return the custom value.
• This change will not impact customers who have hard coded the hostname instead of using the defaultHost value.
Nature of Impact
• Applications managed using Dynamic Content that currently load images from a .ws domain may start loading images from an equivalent .net domain.
• Your frontend monitoring tools may pick up a reduction in images loading from ws domains and see an increase in images loading from a .net domain name.
• The existing .ws hostnames will continue to work and there are currently no plans to deprecate them so that customers who may have hard coded a .ws image URL are not impacted.
Jan 28, 11:58 GMT