Remove Instance Names from URLs for Visualforce, Community Builder, Site.com Studio, and Content Files (Critical Update)

We’re stabilizing the hostname of Visualforce, Community Builder, Site.com Studio, and content file URLs by removing instance names from URLs. This critical update applies to orgs that have a deployed My Domain. It will be activated automatically on March 16, 2019.
Available in: Salesforce Classic and Lightning Experience
Available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

Prior to Winter ’18, Visualforce, Community Builder, Site.com Studio, and content file URLs included the instance name of the org, even when a My Domain name was deployed. An instance name identifies where your Salesforce org is hosted.

When we remove the instance name from your URLs, your hostnames change.

Here are two examples:
  • mydomain--c.visualforce.com replaces mydomain--c.na1.visual.force.com
  • mydomain--c.documentforce.com replaces mydomain--c.na1.content.force.com
Note

Note

All *.content.force.com URLs will be replaced with *.documentforce.com.

After this update, a URL that includes the instance name, such as a bookmark, automatically redirects to the new hostname.

This update might log out users who are accessing Visualforce, Community Builder, Site.com Studio, and content file URLs. To minimize disruption, consider activating this critical update during off-peak hours.

Test This Critical Update

We recommend that you test this update in a sandbox to ensure that the new URLs work with firewalls and proxy servers in the network path between your users and Salesforce. Firewalls and proxy servers that filter by hostname must also trust the following:
  • *.visualforce.com
  • *.documentforce.com
  • *.salesforce-communities.com