400 error displayed when sharing page to facebook - facebook

When sharing page to Facebook from website the facebook share window reports that the page url is returning a 400 error and is not shareable. In contrast the Facebook debugger tool reports that the page is OK after rescraping.
I am expecting that since the url is displayed when requested, that sharing to Facebook would not be an issue.
Wondering if anyone has experienced this issue before and if so what was done to resolve the issue
Further details:
When using the facebook debugger tool and rescraping the page url it is reported that the page is OK. Regardless of the number of times that the page is scraped using the debugging tool subsequent shares to facebook from the site page fail with the same error.
Affected web page

Related

Facebook showing wrong tumblr on sharing, 302 redirects to main page

I have a problem. I want to share my blog post on facebook http://videoefekt.cz/?p=548 but every time I do that, it only shows tumblr of my homepage....Facebook debugger is showing Canonical URL is videoefekt.cz, but it shouldnt be. I am also getting "The following required properties are missing: og:image, fb:app_id" warning.... Its a wordpress website, I tried to change permalinks, tried to erase facebook cache and I don know what else to try, can anyone help ?

Sharing URL On Facebook using Addthis

we have a news website and using AddThis plugin to share news on Facebook ,
sometimes when we try to share news on Facebook it doesn't detect the page info (title ,desc , image ) and when we put the same URL on Facebook debugger every thing running correctly and
page info detected , and when return to the web site and use the same URL we can share it normally .
the web site created using asp.net 4.0 + SQL server 2008 + iis 6 and the website behind a firewall
thanks
===
( Update )..
after trying Facebook debugger i got this error :
"Error Parsing URL: Error parsing input URL, no data was scraped. "
and after trying it after 2 days i can share the link without use the debugger .
then i try the debugger and it's working with out error (same link )
Facebook uses a lot of caching especially for shared links. Once a user has shared a link, Facebook will cache the title, test and images it scraped from that URL.
When you pass a URL though the Facebook Debugger, Facebook will clear it's cache on that URL and use the new data. So the actual act of passing the URL though the debugger is what is causing the differences.
Usually you'll only pass the URL though the debugger again when something has changed on that URL and you want it Facebook to know about it.
The Facebook URL debugger also serves to re-scrape the page, so if you're having trouble with sharing the wrong data to Facebook run it through there to refresh their caches.

The facebook debugger is giving 500 error

The facebook debugger is giving 500 error for your webpage. It is unable to get my og metatags values. However, og metatags are present in the web page:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fstaging.eco.ca%2Fcommunity%2Fblog%2F5-fascinating-green-jobs-youve-never-heard-of%2F68170%2F
Take a look at your IIS configuration. Something in there is refusing connections from anything that isn't a web browser.
Your page returns a 500 error for the W3C validator also.
For me it was because when Facebook, Google or other robots access the page, they don't send a language like a browser does, and in the code we were using the browser language to determine the content language.
I want to share my experience about this facebook debugger 500 error. I was getting this error without any explanation on facebook debugger. I checked my server side and domain records, tried what I found on internet with no luck. It took me long time to discover the problem.
Problem was I was sharing url within a restricted area in my website while sharing for first time. Let me explain, I have a test page in my cms, before I publish anything, I test if everything's ok. I realised whenever I test a content, facebook tries to crawl site, but it's in a restricted area. So I moved anything about facebook from my test page.

"URL is unreachable" error for Facebook comments box being cached?

Our website uses the Facebook Comments Box plugin. We include the comments box on our staging site that is behind our firewall, which means Facebook can't access it and generates the "URL is unreachable" error. This I understand.
However, once a page is published, and is reachable by Facebook, the error is still displayed. This can be easily fixed by clicking on the debug link provided along with the error, but my content editors don't want to have to do this every time, and they sometimes forget.
It seems like the reachable status is cached and reset once you use the debugger. Can anyone think of another explanation?
I suppose I could omit the Facebook comments box from the staging site, but would prefer not to. Any other ideas?
In the documentation of the Like Button they explain when the page is being scraped :
When does Facebook scrape my page?
Facebook needs to scrape your page to know how to display it around
the site.
Facebook scrapes your page every 24 hours to ensure the properties are
up to date. The page is also scraped when an admin for the Open Graph
page clicks the Like button and when the URL is entered into the
Facebook URL Linter. Facebook observes cache headers on your URLs - it
will look at "Expires" and "Cache-Control" in order of preference.
However, even if you specify a longer time, Facebook will scrape your
page every 24 hours.
The user agent of the scraper is: "facebookexternalhit/1.1
(+http://www.facebook.com/externalhit_uatext.php)"
Here are three options:
You can call the debugger by issuing a simple http request, you can do that from the server when you publish your article (or what ever you're publishing), you don't have to use the debugger tool.
You can check the user agent string for requests and if it's the facebook scraper allow it so that it can cache the page.
You can use different urls for production and staging, that way the cache of the staging pages won't matter in production.

Problem with open graph when posting to facebook

I'm trying to integrate open graph in my website, so that I can post a link to my relevant facebook page and it will display the relevant information (title, description etc).
Yet, even though it worked for some time, now it only displays my domain name regardless of the link I post. No images, no descs, nothing.
I've created a test page to find out what's wrong, but I've come to a dead end.
The test page is W3C valid, the Facebook debugger is parsing all the information correctly, the preview before I post the link to facebook is correct, but when I hit post it displays nothing, just the url.
I've tried several actions such as different doctypes, commenting out the open graph metas, moving js after the metas, removing the meta content-type to no avail, but if you can help me post the test page correctly to facebook, I think I'll be able to find what's wrong with my site.
My website: http://www.accorda.info
The test page: http://www.accorda.info/test.html
My facebook fan page: http://www.facebook.com/accorda.info
Replace the meta tag or delete some. I don't understand… Facebook OpenGraph Debug tool show IMBb info for your page.
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.accorda.info%2Ftest.html
Remember, Facebook don't update page info real-time. New meta tags can be visible in 2 days.