This error is particularly common for custom web applications for a handful of reasons: Many of them are using a custom Facebook application. This is sometimes necessary, and it's the best way to ensure that your developers have the proper permissions to access whichever user's information that they need. Business applications are often separate from any Facebook application. This makes it much easier to have different servers for back-end and front-end functions. It is however necessary to use HTTP redirects for developers with access to custom Facebook applications. Newer Facebook servers will not redirect these URLs. So you will need to fix what causes them to return the 400 error first.
it can be resolved but you need to visit https://developers.facebook.com/tools/lint/?url=https%3A%2F%2Fdevelopers.facebook.com%2Fken%2Fapps%2F%3Fapp_id%3D867550014171853%26secret_token%3D6AvlwtIFGSjk4u1J0Gso5Q%3Bhttp%253A%252F%252Fd0bcf361bfb000009292025b212059984.apps.facebook.com%2526locale%253Den_US%2526test_user%253DooLuh86754BK73%2523_auth_client%253Dfb.mobile&domain=local.
How do I know when I need to use the HTTP redirect? The best way to know whether or not to use HTTP redirects is to use the URL Linter tool in the Facebook Developer app. URL Linter can be found under the Tools tab in the Developer app. d2c66b5586