Upcoming HTTPS Certificate Change - YouTube APIs Announcement Forum

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Upcoming HTTPS Certificate Change
Date: Tue, 13 Nov 2012 07:41:49 -0800 (PST)
From: Jeffrey Posnick <je...@google.com>
To: youtube-api@googlegroups.com
Message-Id: <9028fefc-f85a-4d2f-a087-0155390ec4fe@googlegroups.com>
Subject: Upcoming HTTPS Certificate Change
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1459_6013830.1352821309373"

------=_Part_1459_6013830.1352821309373
Content-Type: multipart/alternative; 
	boundary="----=_Part_1460_8494824.1352821309373"

------=_Part_1460_8494824.1352821309373
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

*If you=E2=80=99re a developer who uses the YouTube API, and if you make yo=
ur=20
requests to the API using HTTPS, there=E2=80=99s an upcoming change that yo=
u should=20
be aware of. Sometime in early 2013, Google will be changing the=20
certificates used for establishing secure HTTPS connections to all of our=
=20
servers, in what we anticipate will be a backwards-compatible manner.=20
Still, since there are so many slight differences in HTTPS client=20
implementations, we encourage you to test your existing code in advance of=
=20
this change and to report any issues<https://code.google.com/p/gdata-issues=
/issues/entry?template=3DYouTube%20(Defect%20Report)>that you do encounter.

To confirm compatability today in advance of the production change, you can=
=20
make test API requests to stage.gdata.youtube.com and=20
uploads.stage.gdata.youtube.com using version 1, 2, or 2.1 of the Data API,=
=20
as described in this blog post<http://apiblog.youtube.com/2008/11/all-world=
s-stage.html>about our staging environment. The new certificates are alread=
y in place on=20
those servers. Be sure that you=E2=80=99re using https:// as the protocol.

If you=E2=80=99re using HTTP instead of HTTPS to access the YouTube Data AP=
I then=20
you also won=E2=80=99t be affected by the new security certificates=E2=80=
=94but you really=20
should start using HTTPS!

Developers who still rely on ClientLogin<https://developers.google.com/yout=
ube/2.0/developers_guide_protocol_clientlogin>for handling authorization (w=
hich we also don=E2=80=99t=20
recommend <http://apiblog.youtube.com/2011/03/clientlogin-fail.html>) have=
=20
one additional thing to test, even if your actual YouTube API requests=20
don=E2=80=99t use HTTPS: ClientLogin requests are made=20
https://www.google.com/accounts/ClientLogin. Because we do not have a=20
staging domain name set up for www.google.com, the recommended way of=20
testing ClientLogin in advance of the certificate change is to hardcode the=
=20
IP address 74.125.130.105 for the domain name www.google.com in the=20
/etc/hosts <http://en.wikipedia.org/wiki/Hosts_(file)> file of your=20
computer. Be sure to remove that entry when you=E2=80=99re done testing.

We don=E2=80=99t yet have a specific date in mind for making the switch in=
=20
production, and when we do, it will be added as an update to this blog=20
post. Please don=E2=80=99t wait until the last minute to test your code, th=
ough!

Cheers,
=E2=80=94Jeff Posnick <https://plus.google.com/117780118136555864520/posts>=
, YouTube=20
API Team <http://google.com/+YouTubeDev>*

------=_Part_1460_8494824.1352821309373
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<b id=3D"internal-source-marker_0.44895861856639385" style=3D"color: rgb(0,=
 0, 0); font-family: Arial, sans-serif; line-height: 18.90625px; font-weigh=
t: normal;"><span style=3D"font-family: Arial; font-size: 15px; white-space=
: pre-wrap;">If you=E2=80=99re a developer who uses the YouTube API, and if=
 you make your requests to the API using HTTPS, there=E2=80=99s an upcoming=
 change that you should be aware of. Sometime in early 2013, Google will be=
 changing the certificates used for establishing secure HTTPS connections t=
o </span><span style=3D"font-family: Arial; font-size: 15px; font-weight: b=
old; white-space: pre-wrap;">all</span><span style=3D"font-family: Arial; f=
ont-size: 15px; white-space: pre-wrap;"> of our servers, in what we anticip=
ate will be a backwards-compatible manner. Still, since there are so many s=
light differences in HTTPS client implementations, we encourage you to test=
 your existing code in advance of this change and to </span><a href=3D"http=
s://code.google.com/p/gdata-issues/issues/entry?template=3DYouTube%20(Defec=
t%20Report)" style=3D"color: rgb(0, 51, 204);"><span style=3D"color: rgb(17=
, 85, 204); font-family: Arial; font-size: 15px; white-space: pre-wrap;">re=
port any issues</span></a><span style=3D"font-family: Arial; font-size: 15p=
x; white-space: pre-wrap;"> that you do encounter.</span><br><span style=3D=
"font-family: Arial; font-size: 15px; white-space: pre-wrap;"></span><br><s=
pan style=3D"font-family: Arial; font-size: 15px; white-space: pre-wrap;">T=
o confirm compatability today in advance of the production change, you can =
make test API requests to </span><span style=3D"font-family: 'Courier New';=
 font-size: 15px; white-space: pre-wrap;">stage.gdata.youtube.com</span><sp=
an style=3D"font-family: Arial; font-size: 15px; white-space: pre-wrap;"> a=
nd </span><span style=3D"font-family: 'Courier New'; font-size: 15px; white=
-space: pre-wrap;">uploads.stage.gdata.youtube.com</span><span style=3D"fon=
t-family: Arial; font-size: 15px; white-space: pre-wrap;"> using version 1,=
 2, or 2.1 of the Data API, as described in </span><a href=3D"http://apiblo=
g.youtube.com/2008/11/all-worlds-stage.html" style=3D"color: rgb(0, 51, 204=
);"><span style=3D"color: rgb(17, 85, 204); font-family: Arial; font-size: =
15px; white-space: pre-wrap;">this blog post</span></a><span style=3D"font-=
family: Arial; font-size: 15px; white-space: pre-wrap;"> about our staging =
environment. The new certificates are already in place on those servers. Be=
 sure that you=E2=80=99re using </span><span style=3D"font-family: 'Courier=
 New'; font-size: 15px; white-space: pre-wrap;">https://</span><span style=
=3D"font-family: Arial; font-size: 15px; white-space: pre-wrap;"> as the pr=
otocol.</span><br><span style=3D"font-family: Arial; font-size: 15px; white=
-space: pre-wrap;"></span><br><span style=3D"font-family: Arial; font-size:=
 15px; white-space: pre-wrap;">If you=E2=80=99re using HTTP instead of HTTP=
S to access the YouTube Data API then you also won=E2=80=99t be affected by=
 the new security certificates=E2=80=94but you really should start using HT=
TPS!</span><br><span style=3D"font-family: Arial; font-size: 15px; white-sp=
ace: pre-wrap;"></span><br><span style=3D"font-family: Arial; font-size: 15=
px; white-space: pre-wrap;">Developers who still rely on </span><a href=3D"=
https://developers.google.com/youtube/2.0/developers_guide_protocol_clientl=
ogin" style=3D"color: rgb(0, 51, 204);"><span style=3D"color: rgb(17, 85, 2=
04); font-family: Arial; font-size: 15px; white-space: pre-wrap;">ClientLog=
in</span></a><span style=3D"font-family: Arial; font-size: 15px; white-spac=
e: pre-wrap;"> for handling authorization (which we also </span><a href=3D"=
http://apiblog.youtube.com/2011/03/clientlogin-fail.html" style=3D"color: r=
gb(0, 51, 204);"><span style=3D"color: rgb(17, 85, 204); font-family: Arial=
; font-size: 15px; white-space: pre-wrap;">don=E2=80=99t recommend</span></=
a><span style=3D"font-family: Arial; font-size: 15px; white-space: pre-wrap=
;">) have one additional thing to test, even if your actual YouTube API req=
uests don=E2=80=99t use HTTPS: ClientLogin requests are made </span><a href=
=3D"https://www.google.com/accounts/ClientLogin" style=3D"color: rgb(0, 51,=
 204);"><span style=3D"color: rgb(17, 85, 204); font-family: Arial; font-si=
ze: 15px; white-space: pre-wrap;">https://www.google.com/accounts/ClientLog=
in</span></a><span style=3D"font-family: Arial; font-size: 15px; white-spac=
e: pre-wrap;">. Because we do not have a staging domain name set up for </s=
pan><span style=3D"font-family: 'Courier New'; font-size: 15px; white-space=
: pre-wrap;">www.google.com</span><span style=3D"font-family: Arial; font-s=
ize: 15px; white-space: pre-wrap;">, the recommended way of testing ClientL=
ogin in advance of the certificate change is to hardcode the IP address </s=
pan><span style=3D"font-family: 'Courier New'; font-size: 15px; white-space=
: pre-wrap;">74.125.130.105</span><span style=3D"font-family: Arial; font-s=
ize: 15px; white-space: pre-wrap;"> for the domain name </span><span style=
=3D"font-family: 'Courier New'; font-size: 15px; white-space: pre-wrap;">ww=
w.google.com</span><span style=3D"font-family: Arial; font-size: 15px; whit=
e-space: pre-wrap;"> in the </span><a href=3D"http://en.wikipedia.org/wiki/=
Hosts_(file)" style=3D"color: rgb(0, 51, 204);"><span style=3D"color: rgb(1=
7, 85, 204); font-family: 'Courier New'; font-size: 15px; white-space: pre-=
wrap;">/etc/hosts</span></a><span style=3D"font-family: Arial; font-size: 1=
5px; white-space: pre-wrap;"> file of your computer. Be sure to remove that=
 entry when you=E2=80=99re done testing.</span><br><span style=3D"font-fami=
ly: Arial; font-size: 15px; white-space: pre-wrap;"></span><br><span style=
=3D"font-family: Arial; font-size: 15px; white-space: pre-wrap;">We don=E2=
=80=99t yet have a specific date in mind for making the switch in productio=
n, and when we do, it will be added as an update to this blog post. Please =
don=E2=80=99t wait until the last minute to test your code, though!</span><=
br><span style=3D"font-family: Arial; font-size: 15px; white-space: pre-wra=
p;"></span><br><span style=3D"font-family: Arial; font-size: 15px; white-sp=
ace: pre-wrap;">Cheers,</span><br><span style=3D"font-family: Arial; font-s=
ize: 15px; white-space: pre-wrap;">=E2=80=94</span><a href=3D"https://plus.=
google.com/117780118136555864520/posts" style=3D"color: rgb(0, 51, 204);"><=
span style=3D"color: rgb(17, 85, 204); font-family: Arial; font-size: 15px;=
 white-space: pre-wrap;">Jeff Posnick</span></a><span style=3D"font-family:=
 Arial; font-size: 15px; white-space: pre-wrap;">, </span><a href=3D"http:/=
/google.com/+YouTubeDev" style=3D"color: rgb(0, 51, 204);"><span style=3D"c=
olor: rgb(17, 85, 204); font-family: Arial; font-size: 15px; white-space: p=
re-wrap;">YouTube API Team</span></a></b><br>
------=_Part_1460_8494824.1352821309373--

------=_Part_1459_6013830.1352821309373--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
