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

[THREDDS #MNI-826584]: Godiva 2 wms server configuration

Hi Patrick,

I don't believe we can configure as you are asking.  However, I do know that 
other ESRL groups have TDS instances running behind proxy servers.  I contacted 
one group, and found out the following trouble-shooting steps:

Rename the thredds war file in webapps.  For Patrick it would need to be
named  gsd#thredds.war .  This will allow tomcat to handle the uri properly.

Also in WEB-INF/web.xml set ContextPath parameter to gsd/thredds .

All the entries in catalog.xml need to have the base for each service
set to /gsd/thredds/... .

Also I have an apache config file for thredds the is :

ProxyPreserveHost Off

ProxyPass /psd/thredds   ajp://localhost:8009/psd/thredds retry=2
ProxyPassReverse /psd/thredds  ajp://localhost:8009/psd/thredds

CacheDisable http://localhost
<Location /psd/thredds>
        ProxyPass http://localhost:8080/psd/thredds
        ProxyPassReverse http://localhost:8080/psd/thredds
        order allow,deny
        allow from all
</Location>

Fixing the proxy server configuration should eliminate the issue you are seeing 
with the self-referential URI in the Godiva2 link.

-Lansing

> Hey Lansing,
> 
> I understand what you're saying about the information being passed from
> apache. I was thinking more along the lines of changing something so that a
> view link for Godiva2 would not appear when I enabled the wms service.
> 
> By way of comparison when I only enable a 'http' service for a data
> product, TDS doesn't generate a Godiva2 viewer link for it; it only
> presents a viewer link for 'NetCDF-Java ToolsUI (webstart)' My hope was
> that I could disable the generation of the Godiva2 links altogether (which
> are problematic and not needed by me) and still offer the WMS service
> (which I do need)
> 
> regards,
> Patrick
> 
> 
> address@hidden> wrote:
> 
> > Patrick,
> >
> > That information is used everywhere (see the opening page of the catalog
> > here, for instance: http://esrl.noaa.gov/gsd/thredds/catalog.html).  The
> > TDS is just taking the information that apache is passing on through the
> > proxy, not creating it.
> >
> > -Lansing
> >
> > On 4/30/2013 4:02 PM, Patrick Hildreth - NOAA Affiliate wrote:
> > > New Client Reply: Godiva 2 wms server configuration
> > >
> > > Is it possible to change the configuration of the TDS so that it doesn't
> > > present the Godiva2 viewer link?
> > >
> > >
> > > address@hidden> wrote:
> > >
> > >> Patrick,
> > >>
> > >> It looks like you are seeing an issue with your proxy configuration,
> > not a
> > >> TDS problem per se.  We have a FAQ on the issue here:
> > >>
> > >>
> > >>
> > http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.3/faq.html#proxyServerAndGeneratedURLs
> > >>
> > >> -Lansing
> > >>
> > >> Ticket Details
> > >> ===================
> > >> Ticket ID: MNI-826584
> > >> Department: Support THREDDS
> > >> Priority: Normal
> > >> Status: Open
> > >>
> > >>
> > >
> > >
> > > Ticket Details
> > > ===================
> > > Ticket ID: MNI-826584
> > > Department: Support THREDDS
> > > Priority: Normal
> > > Status: Open
> > > Link:
> > https://www.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=22000
> >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: MNI-826584
> > Department: Support THREDDS
> > Priority: Normal
> > Status: Open
> >
> >
> 
> 


Ticket Details
===================
Ticket ID: MNI-826584
Department: Support THREDDS
Priority: Normal
Status: Open