Without the original context, this is nearly impossible to understand. Facebook does not serve the same source code to everyone. Based on your user agent, location, A/B test group, and login status, Facebook’s servers generate a custom bundle. Viewing source as a logged-out user reveals a completely different (and much simpler) page than viewing source as a logged-in user. Part 4: The Special Case of "web.facebook.com" You may have noticed the subdomain web.facebook.com . This is Facebook’s legacy mobile web interface, designed for older browsers or users who deliberately block the main facebook.com domain (often due to DNS filtering or enterprise policies).
If you view source on https://web.facebook.com , you will see a slightly more traditional HTML structure. There are still scripts, but you might actually spot visible <div> and <span> tags containing profile names or post text. view sourcehttpsweb facebook
Reality: The view-source: prefix works over HTTPS just fine. Your browser still establishes a secure connection. The only difference is that the browser renders text instead of executing it. Without the original context, this is nearly impossible
Example of minified code you might see: for(var d=0;d<e.length;d++){f.push(g[e[d]])} Viewing source as a logged-out user reveals a