Facebook Object Debugger
By
Arif Rahman
—
May 18, 2017
—
Facebook
Facebook object debugger - One typically essential, and ignored the element of modern-day web advancement is Open Chart tags. You understand, those meta tags with unique characteristics that break your page recognition? That's an entirely another subject though.
Today, I wish to discuss the Facebook Object Debugger and providing it access to an HTTP Auth safeguarded the environment, such as a staging or pre-launch production website. This is Apache particular, so Nginx fans will need to look in other places.
Presume you have this set up in your Apache config or access;
Today, I wish to discuss the Facebook Object Debugger and providing it access to an HTTP Auth safeguarded the environment, such as a staging or pre-launch production website. This is Apache particular, so Nginx fans will need to look in other places.
Presume you have this set up in your Apache config or access;
1. AuthUserFile/ var/www/staging/. htpasswd.The simplest manner in which I have discovered to make this work is to accept based upon user representative. I initially attempted permitting it based upon IP address. However the debugger utilizes lots of IP addresses, and after I had included a half lots, I quit and changed to user representative.
2. AuthType Basic.
3. AuthName "Secure Location."
4.Need valid-user.
Click to read more:Understand, that because of this, it's rather simple for somebody to phony their UA and access, so I suggest just utilizing this code while you actively use the debugger, and turning it off later on. This likewise avoids leakages if somebody pastes the URL into a real Facebook remark.
1. AuthUserFile/ var/www/staging/. htpasswd.Pretty simple!
2. AuthType Basic.
3. AuthName "Secure Location."
4. Need valid-user.
5.
6. # Enable from Facebook.
7. SetEnvIfNoCase User-Agent facebookexternalhit. * facebook.
8. Order allow, reject.
9. Enable from env= facebook.
10. Please Any.