Re: [thredds] HTTPS support for remote catalogs

I checked the code and it indeed only supports HTTP.
I will open a ticket on this and have it fixed.
Thank you for finding this.
=Dennis Heimbigner
 Unidata

On 11/10/2016 3:01 PM, Georgi Kostov - NOAA Affiliate wrote:
Hello, THREDDS list,


We have a working catalogRef entry for a remote service which looks like
this:

  <catalogRef name="ABC"

    xlink:title="ABC dataset"

    xlink:href="http://host.domain.gov/thredds/catalog/abc/catalog.xml"; />


When I change the scheme in the URL from HTTP to HTTPS (i.e.
xlink:href=”https://...) I get the following error:


“HTTP Status 400 - Bad request: The "catalogUri" field must be an HTTP URI.

------------------------------------------------------------------------

typeStatus report

messageBad request: The "catalogUri" field must be an HTTP URI.

descriptionThe request sent by the client was syntactically incorrect.”


The results are the same on both TDS 4.2 and 4.3 (on my end).

They sit behind Apache httpd, which proxies for the tomcat instances.

The remote service is TDS 4.2.

My question is whether TDS remote catalog definitions support
HTTPS-based service URLs.

If so, then what is missing from my catalog xmls?

If not, then is there a later version of TDS that provides such support?


Many thanks in advance,

Georgi



--
Georgi Kostov
Team ERT/STG, US Government Contractor
Data Access Branch, NOMADS/NCMP Team| NOAA Mail code E/NE54
NOAA's National Centers for Environmental Information (NCEI)
151 Patton Ave., Suite 468, Asheville, NC 28801-5001
georgi.kostov@xxxxxxxx <mailto:georgi.kostov@xxxxxxxx> | (828) 271-4921
| http://nomads.ncdc.noaa.gov/
GPG Key ID 0xE2BD9A06. Fingerprint: 5109 7E85 D528 5E10 E516 BB80 AA42
52F1 E2BD 9A06

Follow NCEI on Facebook
<http://www.facebook.com/NOAANationalClimaticDataCenter> and Twitter
<http://www.twitter.com/NOAANCDC>
/
/The contents of this message are mine personally and do not necessarily
reflect any position of NOAA or STG. This electronic transmission
contains information that may be internal use only, confidential, or
proprietary.  If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents hereof is
strictly prohibited.  If you have received this transmission in error,
please notify Georgi.Kostov@xxxxxxxx <mailto:Georgi.Kostov@xxxxxxxx>


_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web.  Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.


thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/




  • 2016 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: