Image showing in Validation - not on Twitter.com


#1

Hi,

I’m validating the following URL in the Card Validator and it renders properly (no errors):

http://inpoli.com/glensavoie/posts/2014/ballot-packed-for-saint-john-east-byelection

For actual Tweets referencing this URL on Twitter.com, the image does not render in the Tweet.

Any ideas why this isn’t consistent - anything that I can do to resolve?


#2

Something odd here for sure.

It looks like your image is stored on another server.

$ curl -v http://inpoli.com/getattachment/967b34a6-041d-47e2-89c4-cc6eecce4b04/GlenSavoie/Posts/2014/Ballot-packed-for-Saint-John-East-byelection
* Hostname was NOT found in DNS cache
*   Trying 191.238.13.3...
* Connected to inpoli.com (191.238.13.3) port 80 (#0)
> GET /getattachment/967b34a6-041d-47e2-89c4-cc6eecce4b04/GlenSavoie/Posts/2014/Ballot-packed-for-Saint-John-East-byelection HTTP/1.1
> User-Agent: curl/7.37.1
> Host: inpoli.com
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Cache-Control: public, must-revalidate
< Transfer-Encoding: chunked
< Content-Type: text/html
< Expires: Wed, 04 Nov 2015 14:00:40 GMT
< Location: https://az589936.vo.msecnd.net/cmsstorage/inpoli/files/96/967b34a6-041d-47e2-89c4-cc6eecce4b04.jpg
* Server Microsoft-IIS/8.5 is not blacklisted
< Server: Microsoft-IIS/8.5
< X-Frame-Options: SAMEORIGIN
< X-AspNet-Version: 4.0.30319
< X-Powered-By: ASP.NET
< Date: Tue, 04 Nov 2014 14:00:40 GMT
<
* Connection #0 to host inpoli.com left intact

For some reason I guess the cards crawler may either not be following the 301 redirect, or is encountering some other problem in accessing the image when building the card.


#3

Hi Andy,

The CMS is redirecting image URLs to a copy stored in an Azure CDN.

It does render properly in the validator - shouldn’t it be failing here to be consistant with Twitter.com?

Any suggestions for resolving on the live site?


#4

I agree that it is odd that the two are not consistent…

There’s a chance that the image on the CDN was not available globally at the point at which you first tweeted the link. In that case, the card cache would be holding the card without an image for the first week or so before it is recrawled.

I’ve just manually kicked this link by adding a junk /? to the end of it, and tweeting it again now shows the summary card. This is a slight hack but it causes the cards crawler to revisit and recreate the card. The troubleshooting guide has more on this.