Closed spriggsha closed 9 years ago
triblondon
commented
10 years ago This is a caching issue - we updated the image, but it can be locally cached or cached on Akamai. It's hard to purge Akamai, so we typically just have to wait for it to expire. Are you still seeing it?
spriggsha
commented
10 years ago We do still see it, yes. It's not of particularly high concern, as we still get a Twitter icon either way. I only even noticed it because of the automated visual testing that the team does.
On 30 September 2014 10:38, Andrew Betts notifications@github.com wrote:
This is a caching issue - we updated the image, but it can be locally cached or cached on Akamai. It's hard to purge Akamai, so we typically just have to wait for it to expire. Are you still seeing it?
— Reply to this email directly or view it on GitHub https://github.com/Financial-Times/o-share/issues/29#issuecomment-57289380 .
Harry Spriggs QA Automation Strategic Products
+44 (0)20 787 34914 Number One Southwark Bridge, London SE1 9HL
https://www.facebook.com/financialtimes https://twitter.com/FT http://www.linkedin.com/company/financial-times https://plus.google.com/+FinancialTimes/posts http://www.youtube.com/user/FinancialTimesVideos
This email was sent by a company owned by Pearson plc, registered office at 80 Strand, London WC2R 0RL. Registered in England and Wales with company number 53723.
kaelig
commented
9 years ago Couldn't reproduce the error as of today, looks like caching issues may have been worked out since then.
Seen on the Responsive Fast-FT page
The call to image.webservices.ft.com is the same each time. It's the returned icons that are different. About 50/50 which one you get.
Request URL:http://image.webservices.ft.com/v1/images/raw/ftsocial:link,ftsocial:twitter,ftsocial:facebook,ftsocial:googleplus,ftsocial:linkedin,ftsocial:stumbleupon,ftsocial:reddit,ftsocial:tumblr?width=24&source=o-share
