Since yesterday I cannot post on Facebook I have only an URL without thumbnail, nor metas.
I think that is a problem with like button but any idea how to fix.
Strange because my old articles working normally! only I have problems when I write a new post.
Here is the Facebook debugger info:
Response Code: 503
Fetched URL: http://www.whitewolfpack.com/2012/02/bonnie-marris-wildlife-artist-of_4001.html
Canonical URL: http://www.whitewolfpack.com/2012/02/bonnie-marris-wildlife-artist-of_4001.html
Critical Errors That Must Be Fixed
Error Scraping Page: Bad Response Code
Errors That Must Be Fixed
Missing Required Property: The og:url property is required, but not present.
Missing Required Property: The og:type property is required, but not present.
Missing Required Property: The og:title property is required, but not present.
Open Graph Warnings That Should Be Fixed
Inferred Property: The og:url property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property: The og:title property should be explicitly provided, even if a value can be inferred from other tags.
URLs
Graph API: http://graph.facebook.com/10150624491404835
Scraped URL: See exactly what our scraper sees for your URL
http://www.whitewolfpack.com/2012/02/bonnie-marris-wildlife-artist-of_4001.html
www.whitewolfpack.com
Critical Errors That Must Be Fixed
Error Scraping Page: Bad Response Code
HTTP Response Code: 503
For more information about response codes, see: http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance).[2] Generally, this is a temporary state.
Your might be in a load balanced environment where a bad server is still in rotation.
Related
In facebook for developers, when I am checking a URL in haring debugger, I am getting a response code of 206 with the following error:
Inferred Property: The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
Is it some tag I am missing that is causing a response code of 206 to be returned along with warnings rather than response code of 200.
In my TYPO3 9 LTS installation, when a request with an invalid (i.e. no TypoScript-configured) type number (PAGE.typeNum) comes in, my installation returns an ugly error message:
Example request: https://www.example.com?type=1234
Example response:
Service Unavailable (503)
The page is not configured! [type=1234][]. This means that there is no TypoScript object of type PAGE with typeNum=1234 configured.
More information regarding this error might be available online.
The more information link points to https://typo3.org/go/exception/CMS/1294587217 , but there currently isn't any helpful information how to better configure my installation.
These error messages are also annoying as they may be triggered by webcrawlers and each request creates an error entry in the TYPO system protocol.
What can I do to fallback to/serve the default type=0 HTML page if a requested type number is not configured?
AFAIK TYPO3 can currently not properly handle that. A 503 is generated, but the according errorHandler in the site configuration is not triggered.
At least the error message will be a bit less ugly ("Ooops, an error...") when you are in TYPO3_CONTEXT=Production ...
There is a feature request to make the unknown page type behave like 404: https://forge.typo3.org/issues/86844
For the time being I suggest adding redirects (301) for all types that you do not want to serve outside of TYPO3 (e.g. .htaccess RewriteRules or nginx rewrites).
I want to publish my first Facebook application and a Privacy Policy URL is required.
I have the page privacypolicy.html published in my website but I get the next message when I configure it in "App Details":
You must submit a valid Privacy Policy URL in order to be compliant with Facebook Platform. Request failed with error:
Bad Response Code: URL returned a bad HTTP response code.
The http code returned when I request the page is 200
Any ideas?
The URL is cached by facebook.
Adding # at the end of my Url did the job ..
This is an old question I know, but I figured I'd post my solution and hope it helps anyone. For me I got this error because I had rewrite rules that didn't catch the URL that Facebook actually goes to in order to get the privacy policy. Facebook adds a query string to the URL that you give it for the privacy policy and since my privacy policy page doesn't do anything with the query string, I didn't check for it in my rewrite rule.
You can check out how Facebook scrapes the page you give it by going to Facebook's Sharing Debugger and putting your URL in the input bar. You can also see the last time that Facebook tried to scrape that URL and tell Facebook to try again once you've fixed any issues. This will get around the caching that was mentioned in user2390340's post.
Facebook externalhit appears to request via the ipv6 address published in DNS if there is one available and won't check on the ipv4 published in DNS.
If your website doesn't have ipv6 enabled it'll return a 404 or 500 and you'll get that error "Bad Response Code: URL returned a bad HTTP response code" for your Privacy Policy URL.
Edit:
Also noted that Facebook caches the URL, I was checking it and getting a "bad response code" error even though there was no hit from their UA in the access logs.
Adding ?stuff onto the end of the URL in the Privacy Policy field bypassed a cache and the access log hits showed up with 200 OK, allowing the URL to be saved.
Not sure if this is related to user2259887's comment about Facebook using IPV6 DNS. But after reading his comment, I was able to work around the validation issue by specifying an IP Address URL instead of using the host domain name URL.
This workaround will not work well if the site IP address is dynamic or change often.
I am writing a web scraper and I use WWW::Mechanize module. I am performing a post, and pass invalid values to the arguments of the post. What I extracting is all the links from that page and print them to a text file. I would say that it's ok because the text file is empty which means that the page was not found but my problem is that the success() method is ok, and the status() method is 200.
I know it sounds a little strange but I try to get a page not found status or something to know that the page is not valid.
Does anyone have any idea of what is happening?
Whether or not your code will work depends on how the target site responds to requests for missing pages. If the server handles it by serving up an error page, you will get a successful (200) response, even though the page you requested isn't there.
More information from Google on "soft 404s" -- where missing pages return a valid page.
Here is an example from SO of configuring Apache to return a 200 response instead of a 404:
How can I replace Apache HTTP code 404 to 200
For sharing content we use the facebook share dialog. This used to work fine until several weeks ago. We did not change anything on our side. I get two errors from the facebook debug tool. One about an og property not set (but it is) and a curl SSL error.
An example of a link we share is:
https://www.globalpetalert.com/web/en/pets/missing/8906/
All necessary open graph parameters have been set.
The errors from the debug tool:
Object at URL 'https://www.globalpetalert.com/web/en/pets/missing/8906/' of type 'website' is invalid because a required property 'og:title' of type 'string' was not provided.
Curl Error : SSL_CONNECT_ERROR error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
The og:title is provided.
The SSL_CONNECT_ERROR I do not understand.
Any help is appreciated.