Apex Code Development You need to sign in to do that
Don't have an account?
Bulent Dogan Why is Visualforce pages served from salesforce.com instead of force.com in some organizations?
We have a managed package that works at every customer except one. At this customer we are realizing that the salesforce.com domain is used to server the visualforce page. In other orgs, we see that the visualforce pages are served from visual.force.com domain. We know that there is an internal setting that can disable serving VF pages from Salesforce.com domain. However, obviously we are puzzled on why this is enabled for this org vs the others and what the trigger is?
When the pages are served from salesforce.com domain, we get errors such as:
... from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.
Any insight will be appreciated so that when we suggest this solution to our customer, we can also be confident that there is no harm doing this.
When the pages are served from salesforce.com domain, we get errors such as:
... from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.
Any insight will be appreciated so that when we suggest this solution to our customer, we can also be confident that there is no harm doing this.