<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19170"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV dir=ltr align=left>4) now the download proceeds (or not, 403 if the
certificate is not "enough", e.g. if CMIP5 Research group membership is
required, and the certificate doesn't show this)<BR><SPAN
class=084482912-17022012><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=084482912-17022012><FONT color=#0000ff
size=2 face=Arial>Hello Estani,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=084482912-17022012></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=084482912-17022012><FONT color=#0000ff
size=2 face=Arial>I thought there were other problems that lead to 403 at
this stage (or maybe its an earlier stage). One is if the attribute service
times out. (At least thats how I understood it - but I have to admit I'm
not completely sure). I think BADC used to see this fairly frequently
(before they limited the number of concurrent requests from on IP to the data
node), and is one reason getting to MOHC data is sometimes a bit
unreliable. Stephen has more of the details and can correct me if I've
said anything too wrong.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=084482912-17022012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=084482912-17022012><FONT color=#0000ff
size=2 face=Arial>Jamie</FONT></SPAN></DIV></BODY></HTML>