<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This is going to have an impact I think. I’ll investigate.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Flickr Mail [mailto:no-reply-flickrmail@flickr.com] <br><b>Sent:</b> 07 May 2014 18:19<br><b>To:</b> julian.tenney@nottingham.ac.uk<br><b>Subject:</b> Flickr API Going SSL-Only on June 27th, 2014<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We see that you own an active API key for the Flickr API, and wanted make sure you know about some upcoming changes to the API related to SSL. <br><br>As you may have read on the <a href="http://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-27th-2014/">Flickr code blog</a>, we've updated all of the API endpoints to fully support SSL. You no longer need to use a special subdomain to access the API securely, and we want to make sure that all API communication adopts SSL. <br><br>Many of you have moved over to using SSL already, which is great! If you haven't, it shouldn't be much more work than updating your apps to call the API at: <a href="https://api.flickr.com/">https://api.flickr.com/</a> <br><br>We'll be updating the blog with information as we get close to the switchover date, but here's the most important info: <br><br>New API keys will be issued for HTTPS access only: as of 6 May 2014<br>First blackout test window: <b>3 June 2014, 10:00-12:00 Pacific Daylight Time (PDT)</b><br>Second blackout test window: <b>17 June 2014, 18:00-20:00 (PDT)</b><br>Non-SSL API deprecated: <b>27 June 2014, 10:00 (PDT)</b> <br><br>During the blackout tests and after the 27th of June, calls to the Flickr API that are not over SSL will fail with an HTTP error code 403. We will also return an error message with (Flickr) code 95 and msg "SSL is required". <br><br>Here are example error responses: <br><br><b>XML (REST):</b> <br><br><?xml version="1.0" encoding="utf-8" ?> <rsp stat="fail"> <err code="95" msg="SSL is required" /> </rsp> <br><br><b>JSONP:</b> <br><br>jsonFlickrApi({ "stat": "fail", "code": "95", "message": "SSL is required" }) <br><br><b>JSON:</b> <br><br>{ "stat": "fail", "code": "95", "message": "SSL is required" } <br><br>We realize that this change might be more difficult for some. We will follow the <a href="https://groups.yahoo.com/neo/groups/yws-flickr/info">Developer Support Group</a> closely, so please let us hear your questions. <br><br>If you have a question about the API transition to SSL that you feel is unique to your situation or is more appropriate to handle via conversation directly with Flickr, send an email to <a href="mailto:flickr-api-help@yahoo-inc.com">flickr-api-help@yahoo-inc.com</a>. We will monitor that mailbox through July 2014. <br><br>Thank you for being a member of our API community,<br>The Flickreenos <o:p></o:p></p></div></body></html>