In the Network tab, right-click on the request → "Copy" → "Copy Response" to paste the fully rendered output into a diff tool (e.g., Beyond Compare, VS Code Diff) to compare production vs. staging SHTML outputs. Method 3: Server-Side Debugging Modules (For Admins) If you are a server administrator, you can configure your web server to output both the raw SHTML and the parsed version side-by-side. This is the ultimate "extra quality" inspection. Apache Configuration ( httpd.conf or .htaccess ) Enable extended SSI debugging:
This replaces the SSI directive with a visible marker, allowing you to verify if includes are being resolved. Even with the methods above, you may not get "extra quality" results. Here are the top three failure modes: view shtml extra quality
But a common frustration arises: How do you ensure that when you "view shtml extra quality," you are seeing the resolved, fully rendered output rather than the raw, unparsed code? In the Network tab, right-click on the request