Facebook Error Parsing Message Invalid Url
Contents |
Informationen durch Cookies auf und außerhalb von Facebook zu. Weitere Informationen zu unseren Cookies und dazu, wie du die Kontrolle darüber behältst, findest du hier: Cookie-Richtlinie.HilfeforumAnmeldenZurück zum HilfebereichHilfeforumDeutschZurück zu den Top-FragenÄhnliche FragenWas ist eine Facebook-Profil-URL?Wo finde ich meine error parsing input url no data was cached or no data was scraped. wordpress URL?Warum kann ich keine(n) Nutzernamen/Facebook-URL für meine S...Meine url ist von Facebook blockiert, wie facebook debugger document returned no data kann ich das beheben?FB ist unendlich langsam geworden - was tun?Was bedeuted: "1 Beitrag muß noch von Dir bestätigt werden"?Ähnliche FAQ error parsing input url no data was scraped im HilfebereichWie füge ich eine sichere Seitenreiter-URL für eine App auf...Wie erstelle ich einen Nutzernamen für meine Seite?Wie ändere ich den Nutzernamen meiner Seite?Wie verwende ich URL-Parameter?Muss die „Mehr anzeigen“-URL auf der Endkarte einer Carousel...Wie document returned no data facebook scraper ändere ich die URL, die Bestandteil einer Werbeanzeige i...Stelle eine FrageOpen Graph URL Debugger returns "Error parsing input URL, no data was cached..."Etwas ist kaputtTeilen & VerbindenWhen I share a link using link shortners, like bitly, the first post will not correctly scrape the page. However, subsequent posts of the same URL will correctly scrape the page. I found in these instances, according to apache log records, the FB bot/webscraper does
Url Debugger
not even reach the server. After further debugging using the OG URL Debugger, I found that the FIRST post will always generate the following error: "Error parsing input URL, no data was cached, or no data was scraped." However, if you then press "Fetch New Scraped Information" it will correctly grab the data. In both cases, clicking "See exactly what our scraper sees for your URL" always shows the correct page information. Looks to be a bug in the Feed/Dialog API. Please look into this ASAP. Steps to reproduce: 1. shorten a link with bitly. 2. rename the bitly link with a custom UNIQUE tag. this must be a tag that has never been posted to FB, otherwise it will retrieve previously cached data. 3. Use the URL debugger to verify the data that is scraped. 4. Or, post the link using the Feed/Dialog API -- it will return an empty dialog. Performing this operation after #3 will fetch new data, so you will need to try #4 on a new UNIQUE link. Asked about 2 years ago von David Zaretsky40 Bewertungen · 23 Abonnenten · Gesehen von 6.101Gute FrageDiese Frage verfolgen · TeilenAntwortenNeueste AntwortenBeste AntwortenAntwort hinzufügenMöchtest du einen Freund bitten, diese Frage zu beantworten?EntfernenAnfrage sendenWie hilfreich waren die
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or
Facebook Open Graph
posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Site not valid - but it is up vote 5 down vote favorite 1 So, I'm building a website called "dagbok.nu", which is swedish for "diary now" :) Anyway, when creating the Facebook application, it https://www.facebook.com/help/community/question/?id=10153041718989669 claims that the site URL is invalid as well as the app domain. For site url, I used "http://dagbok.nu" and for site domain, I used "dagbok.nu". Please don't reply (as I've seen others do on similar issues) that I should type the site url with the scheme and the domain without - that's exactly what I'm doing. Right, so according to another question here, one could trouble shoot this functionality using FB's own URL scraper, so I did just that: http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fdagbok.nu http://stackoverflow.com/questions/10190649/site-not-valid-but-it-is And the reply: Error Parsing URL: Error parsing input URL, no data was scraped Right, so now I can assume that the reason for it being considered invalid is because of FB not being able to scrape the URL. But why? According to this question, one of the reasons seems to be that FB has deemed the URL insecure or "spammy". I've acquired this domain from a previous owner so this wasn't all that impossible. But when doing the same thing as Matthew in that post - i.e. trying to post in my timeline using the domain "http://dagbok.nu", I didn't get any information. The status box expanded as if to include a thumbnail and information about the link, but it only contained a "(No title)" text and nothing more. So now I don't know what to do. I've tried to check the DIG and NS records from multiple servers around the web, and everyone seems to resolve it correctly, and I've had friends double check the URL from the states as well. I can't understand what's wrong and I have no idea how to ask someone at FB how to resolve this. Does anyone here have a good advice for this? Thanks in advance! :) EDIT When changing the domain to another domain that points to the exact same web server and document_root, it works! So this is definitely a problem with the domain "dagbok.nu" and not with the
ReportsOverviewaccountadadvertiseradGroupadGroupDynamicSearchAdsTargetadGroupRemarketingListTargetbidStrategycampaigncampaignLocationTargetconversionfeedItemfloodlightActivitykeywordnegativeAdGroupDynamicSearchAdsTargetnegativeAdGroupKeywordnegativeAdGroupRemarketingListTargetnegativeCampaignDynamicSearchAdsTargetnegativeCampaignKeywordnegativeCampaignRemarketingListTargetpaidAndOrganicproductAdvertisedproductGroupproductLeadAndCrossSellproductTargetvisitStandard Query ParametersResponse https://developers.google.com/doubleclick-search/v2/standard-error-responses CodesStandard Error Responses Resource SummaryConversionOverviewgetinsertupdateupdateAvailabilityReportsOverviewgenerategetgetFilerequestSavedColumnsOverviewlistTypes https://benbiddington.wordpress.com/2010/04/23/facebook-graph-api-getting-access-tokens/ of ReportsOverviewaccountadadvertiseradGroupadGroupDynamicSearchAdsTargetadGroupRemarketingListTargetbidStrategycampaigncampaignLocationTargetconversionfeedItemfloodlightActivitykeywordnegativeAdGroupDynamicSearchAdsTargetnegativeAdGroupKeywordnegativeAdGroupRemarketingListTargetnegativeCampaignDynamicSearchAdsTargetnegativeCampaignKeywordnegativeCampaignRemarketingListTargetpaidAndOrganicproductAdvertisedproductGroupproductLeadAndCrossSellproductTargetvisitStandard Query ParametersResponse CodesStandard Error Responses Products DoubleClick Search API Reference Standard Error Responses This document identifies no data some of the error codes and messages that Google APIs return. Specifically, the errors listed here are in the global, or default, domain error parsing input for Google APIs. Many APIs also define their own domains, which identify API-specific errors that are not in the global domain. For those errors, the value of the domain property in the JSON response will be an API-specific value, such as youtube.parameter. This page lists errors by their HTTP status codes as defined in RFC 7231. The sample JSON response below demonstrates how a global error is c
have an application with an id 116122545078207, and I am using the URL of this blog (https://benbiddington.wordpress.com) to collect request tokens. [update, 2010-04-29] If ever there was a lesson to read specification and documentation carefully, this is it. Thanks to comments from Joshua Inkenbrandt, Alex and Gene Leybzon I realise why my examples don't work as expected: I have been trying to use a mixture of web server and client_cred authentication flow. As Gene rightly points out, I should have been using user_agent. User-Agent Flow (with a web browser) Following the instructions as specified in section 3.5.1.1., Client Requests Authorization, of the specification, this is a one-step process: Open this in a browser: https://graph.facebook.com/oauth/authorize? type=user_agent& client_id=116122545078207& redirect_uri=http%3A%2F%2Fbenbiddington.wordpress.com& scope=user_photos,email,user_birthday,user_online_presence Note: there are several options for scope. These are called extended permissions. Note: unless you specify offline_access, your tokens will expire as soon as the user signs out of facebook. Note: client_secret is not supplied: [3.5.1. User-Agent Flow] This user-agent flow does not utilize the client secret since the client executables reside on the end user's computer or device which makes the client secret accessible and exploitable. You'll be redirected to: https://benbiddington.wordpress.com/#access_token= 116122545078207| 2.1vGZASUSFMHeMVgQ_9P60Q__.3600.1272535200-500880518| QXlU1XfJR1mMagHLPtaMjJzFZp4. And you have your access token, you can go ahead and use it: https://graph.facebook.com/me?access_token= 116122545078207| 2.1vGZASUSFMHeMVgQ_9P60Q__.3600.1272535200-500880518| QXlU1XfJR1mMagHLPtaMjJzFZp4. According to section 3.5.1. Client Requests Authorization, because we have not supplied the optional secret_type: secret_type OPTIONAL. The access token secret type as described by Section 5.3. If omitted, the authorization server will issue a bearer token (an access token without a matching secret) as described by Section 5.2. we h