Is there any way to check if an image returned by the Tumblr api was removed due to violations?
At the moment it seems the API returns some URLs which link to something like this:
It also does not appear the HTTP request to the img itself is redirected, as it returns a 304 code like everything else.
Related
We ran our Shopify store URL through Facebook's Debugger because we've been having issues sharing the URL on Facebook. When I put my URL in - I get a 403 Forbidden in return along with the following message:
Critical Errors That Must Be Fixed
Bad Response Code - URL returned a bad HTTP response code.
Errors That Must Be Fixed
Missing Required Property - The 'og:type' property is required, but not present.
However, the 'og:type' property IS present, as well as all other required tags - as these tags are built into the theme we are using.
Facebook states it is a Shopify issue and Shopify points the finger back at Facebook. The bottom line is the website itself comes up with no issue and sharing on other social networks, such as LinkedIn, is no issue either.
The URL in question here is http://www.holeinthesheet.com. Try attempting to share this URL on Facebook and you will see what I mean.
I kept getting an warning that og:image wasn't the right dimensions from the Facebook debugger even though it was. Facebook kept falling back to my site's logo instead of the image I specified in the og:image meta element.
I figured out that the cause of this issue was because my image URL was redirecting to Amazon Web Services' S3 storage URL, so therefore the URL I provided for my meta element was a page that sent an HTTP 302 status code. I think the reason why Facebook is not following the redirect is because I don't have any "cache-control" headers sent with the redirection response. However, I'm not familiar with how or what headers need to be set. So, what cache-control headers must I set in order for Facebook to be happy?
The reason I use a redirect is so that my image URLs could dynamically create various sizes based on the parameters included in the URL and cache that resized image on S3. I do a redirect instead of sending data because I'd rather use bandwidth on AWS than on my VPS. I'd like to keep this setup if I can.
Thanks for reading. All help is highly appreciated! :)
Today, I tried to post a link from my website on my wall, but no OG meta information was fetched. Therefore, I went on to Facebook URL Linter to check things for myself and see if OG meta tags are fetched properly.
To my surprise, every link on my website including the domain itself, generated Response code: 302.
My OG tags are well set and they were working fine a few days ago. Following is what the debugger shows for my domain : http://www.price-tag.org
Response Code: 302
Fetched URL: http://price-tag.org/
Canonical URL: http://price-tag.org/
Final URL: http://price-tag.org/WpjZW/
For every page from my website, facebook linter is adding an arbitrary string like above WpjZW.
Please let me know if this is a facebook error or something has gone wrong at my end.
It seems the linter is being sent on a circular redirect loop. It is seeing a 302 redirect.
For http://www.price-tag.org I don't see anything but a 200 response code when I navigate to your website using Firefox.
However, if I remove the www from the url and go to http://price-tag.org, I do see the strange behaviour of the 302s and then a random url like http://price-tag.org/UKXRN/
I would suggest you contact your server admin or web master to see what they have in place that is doing this 302 redirect and strange url characters.
New FB graph API otherwise working great, but when I make a request to a pic the link below calls a http request to get the image picture, resulting in browsers telling me that the page is only partially encryped. Any quick way around this?
https://graph.facebook.com/NAME/picture
There is an answer here: https://stackoverflow.com/questions/3199164#4403576
The solution is to use https://graph.facebook.com/FB_UID/picture?return_ssl_resources=true
I'm testing the post-remove URL call that should be pinged via POST when my Facebook application is removed, but it doesn't seem to be called.
Monitoring the network traffic in firebug and looking at the POST made when removing the app, the POST does not directly call the Post-Remove URL I specified in the app settings, nor does it pass the POST variables I expected per the documentation.
I set up a simple output at the URL specified "remove page called" that I'd expect to see as the response but don't.
Lastly, the URL called should remove database items which do not get removed.
I don't have any evidence that my post-remove URL is getting called at all. It seems I'm not the only one having this issue but not much insight has been provided.
Answer posted by folks on the Facebook Devleoper forums