When an inline Visualforce page is included in a Salesforce Page Layout, accessing a record may redirect the user to an error page displaying "URL No Longer Exists." The URL of that page contains "servlet/servlet.Integration." This error is typically caused by the Clickjack Protection security feature conflicting with the Visualforce page's header settings.
The error often occurs because the Visualforce page uses the standard Salesforce header. If the page does not require the standard header, set the showHeader attribute to false on the apex:page tag. This removes the header and resolves the conflict with Clickjack Protection.
Update your Visualforce page tag as follows — the showHeader="false" attribute tells Salesforce not to render the standard Salesforce header on this page:
<apex:page standardController="SObject" showHeader="false">
Clickjack Protection is a Salesforce security feature that prevents clickjacking attacks on Visualforce pages. When enabled, it can trigger the "URL No Longer Exists" error on inline Visualforce pages that use standard headers. Disabling this setting removes the conflict.
⚠️ Security Note: Disabling Clickjack Protection reduces your org's security posture. Evaluate the risk and consider alternative approaches before disabling this setting in a production org.
To disable Clickjack Protection for Visualforce pages with standard headers:
In API version 38 and above, if the org setting Enable clickjack protection for customer Visualforce pages with headers disabled is turned on (added in Summer '16), the Visualforce page must also include the applyHtmlTag="false" attribute. Without this attribute, the page cannot render properly when showHeader="false" is already set.
Update your Visualforce page tag to include both attributes as shown below:
<apex:page standardController="SObject" showHeader="false" applyHtmlTag="false">
Similar to Option 2, you can disable the Clickjack Protection setting specifically for Visualforce pages that have headers disabled.
⚠️ Security Note: This also reduces org security. Review the implications before applying this in production.
000387058

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.