Re: [netcdfgroup] Secured OpenDAP: location of .httprc file, current working directory and $HOME environment variable

• To: netCDF Mail List <netcdfgroup@xxxxxxxxxxxxxxxx>
• Subject: Re: [netcdfgroup] Secured OpenDAP: location of .httprc file, current working directory and $HOME environment variable
• From: Dennis Heimbigner <dmh@xxxxxxxxxxxxxxxx>
• Date: Tue, 15 Jul 2014 10:53:07 -0600

Unfortunately, I do not have an acct with ESG,
so it is going to be difficult to debug this.
Let me start by asking you to do the following:
1. append the string '#noprefetch&show=fetch&log'
   to your url
2. send me the output of, say, ncdump using the modified url
=Dennis Heimbigner
 Unidata

plieger wrote:
> Hi all,
> 
> I have a question about the netcdf 4.3.2 library and accessing ESGF
> opendap servers which are secured with x509 client authentication.
> 
> I usually store config settings about my certificate and ssl in the
> .httprc file, I have several of them at different places. In the past I
> used the $HOME environment variable to designate which one to use, but
> this does not seem to work with netcdf 4.3.2.
> 
> As described in
> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf/DAP-Support.html
> chapter 4.12.4 HTTP Configuration, you can either set the current
> working directory to this place or export the HOME variable to the
> directory where this file resides. I found this very useful
> functionality (now I have to change the working directory all the time).
> 
> This is an example of such an .httprc file:
> HTTP.SSL.VALIDATE=0
> HTTP.COOKIEJAR=/someplace/.dods_cookies
> HTTP.SSL.CERTIFICATE=/someplace//certs/creds.pem
> HTTP.SSL.KEY=/someplace/creds.pem
> HTTP.SSL.CAPATH=/someplace/esg_trusted_certificates/
> 
> Is it possible to get this back working again?
> 
> Thanks,
> Maarten Plieger
> 
> 

• References:
  • [netcdfgroup] Secured OpenDAP: location of .httprc file, current working directory and $HOME environment variable
    • From: plieger