[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #ZTB-960075]: Thredds + Apache + SSL

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #ZTB-960075]: Thredds + Apache + SSL
  • Date: Wed, 10 Mar 2010 15:24:52 -0700
It appears that a browser request also fails, implying that the problem is on 
the server. Can anyone else confirm that? Im at the airport over a flaky 
wireless proxy.

> Hi Hank,
> 
> I agree with Jeff, looks like a problem in the underlying netCDF-Java 
> library. I'm not sure if the problem is how we deal with the HTTPS itself or 
> that your certificate is self-signed.
> 
> We will dig into it. We're a bit swamped this week so it may take a few days 
> to get back to you.
> 
> Ethan
> 
> Jeff McWhirter wrote:
> > Hank Fisher wrote:
> > > but I am using his IDV plugin, which enables the initial handshake with
> > > the https server.  We still have the problem with -1 as the port value.
> > >
> >
> > The -1 shown in the error message is a red herring. The problem is that it
> > looks like the opendap reading code on the client isn't handling https.
> >
> > I am switching this ticket over to the java/netcdf folks.
> 


Ticket Details
===================
Ticket ID: ZTB-960075
Department: Support netCDF Java
Priority: Urgent
Status: Open