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

[THREDDS #NON-921195]: Hard coding generated URL references

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 #NON-921195]: Hard coding generated URL references
  • Date: Thu, 09 Sep 2010 12:53:50 -0600
Hi Daryl,

Glad that helped. Let us know if you run into any other problems.

Ethan

Daryl Herzmann wrote:
> On Tue, 7 Sep 2010, Unidata THREDDS Support wrote:
> 
> > Most TDS generated URLs are relative to the server (e.g.,
> > "/thredds/dodsC/") or relative the the current document's base URL.
> > There are only a few places where it is necessary to generate absolute
> > URLs. In those cases, the TDS uses information from the incoming HTTP
> > request to construct the generated URLs. It is up to the proxy to send
> > the correct information to the proxied server so the request information
> > will be correct.
> 
> Bingo, that was the issue.  I did not have
> 
> ProxyPreserveHost On
> 
> set with apache.  Thanks for the detailed information!
> 
> daryl

> > We have a web page (possibly a bit out of date) on
> > Tomcat/Apache proxying with mod_proxy and mod_jk:
> >
> > http://www.unidata.ucar.edu/projects/THREDDS/tech/reference/TomcatBehindProxyServer.html
> >
> > that might be useful.


Ticket Details
===================
Ticket ID: NON-921195
Department: Support THREDDS
Priority: Normal
Status: Closed