> But does the Godiva service by any chance make a request that includes the
> name Godiva in
No (unless by chance you have called one of your datasets "Godiva" or something
> Otherwise the only requests you make are to the wms service is that correct?
Correct - the WMS service includes some non-standard custom operations
(GetMetadata) that serve all the JSON documents for the Godiva site. There are
no requests outside the WMS service endpoint.
> One last question - do you include the port number when you form the URL to
> make the request
If the WMS service is not on port 80 the port number needs to be included in
Hope this helps,
From: Roy Mendelssohn [mailto:Roy.Mendelssohn@xxxxxxxx]
Sent: 28 March 2011 15:31
To: Jon Blower
Subject: Re: [thredds] Trouble with Godiva viewer
But does the Godiva service by any chance make a request that includes the
name Godiva in it? Otherwise the only requests you make are to the wms service
is that correct? I have on my own computer a very small version of what we have
set up but without the proxies, and Godiva works fine there, so I am pretty
certain it is in the proxying.
One last question - do you include the port number when you form the URL to
make the request (ie what is the basis for what you use for the requests?
Port numbers give us a lot of heartburn. A can probably proxy those if I know
what is being sent.
On Mar 28, 2011, at 2:22 AM, Jon Blower wrote:
> Hi Roy,
> The Godiva2 viewer makes a number of AJAX requests (with JSON responses) to
> the WMS itself - i.e. the root URI of all these requests is the same as the
> WMS. For example:
> gets the details of the given layer.
> You could try going to our demo Godiva2 site
> (http://www.reading.ac.uk/godiva2) and using something like Firebug to sniff
> the traffic to the server. There is no proxying here so it should be
> reasonably straightforward. Be warned that our Godiva2 server has been
> showing problems recently so you may see some errors!
> I've never tried any kind of proxying between Godiva2 and the WMS - any
> experience you gather here would be very welcome!
> -----Original Message-----
> Hi All:
> The Godiva viewer is failing on our THREDDS. When you try to access it the
> openlayers amp comes up and then a window comes saying "Invalid JSON
> returned from Server" and no data is displayed.
> If I go into debug on Safari I get:
>> Refused to get unsafe header "X-JSON"
> When I when it with Firefox the console error is:
>> Error: [Exception... "A parameter or an operation is not supported by the
>> underlying object" code: "15" nsresult: "0x8053000f
>> (NS_ERROR_DOM_INVALID_ACCESS_ERR)" location:
>> "chrome://jsview/content/jsviewOverlay.js Line: 649"]
>> Source File: chrome://browser/content/tabbrowser.xml
>> Line: 417
> My guess it has to do with all the proxying we do, and Godiva is sending a
> URL that is blocked. Any info on what URI Godiva uses to get its data (how
> can I figure out what it is sending to see if we ned to proxy anything else.
> "The contents of this message do not reflect any position of the U.S.
> Government or NOAA."
> Roy Mendelssohn
> Supervisory Operations Research Analyst
> Environmental Research Division
> Southwest Fisheries Science Center
> 1352 Lighthouse Avenue
> Pacific Grove, CA 93950-2097
> e-mail: Roy.Mendelssohn@xxxxxxxx (Note new e-mail address)
> voice: (831)-648-9029
> fax: (831)-648-8440
> www: http://www.pfeg.noaa.gov/
> "Old age and treachery will overcome youth and skill."
> "From those who have been given much, much will be expected"
> thredds mailing list
> For list information or to unsubscribe, visit:
"The contents of this message do not reflect any position of the U.S.
Government or NOAA."
Supervisory Operations Research Analyst
Environmental Research Division
Southwest Fisheries Science Center
1352 Lighthouse Avenue
Pacific Grove, CA 93950-2097
e-mail: Roy.Mendelssohn@xxxxxxxx (Note new e-mail address)
"Old age and treachery will overcome youth and skill."
"From those who have been given much, much will be expected"