Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hi Ethan,
You're right! It works when I encode all of the &'s as & amp ;. I must've
mistakenly left one un-encoded when I initially wrote in about this: my
apologies for the false alarm. I'm happy to see that this works!, so now my TDS
catalogs will dump the user right into the relevant LAS page.
Cheers,
John
> Date: Thu, 08 Jul 2010 11:16:06 -0600
> From: Ethan Davis <edavis@xxxxxxxxxxxxxxxx>
> To: thredds@xxxxxxxxxxxxxxxx
> Subject: Re: [thredds] ampersands not working in viewer property URL
> Message-ID: <4C3607D6.6060609@xxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi John,
>
> I get the same message with a straight ampersand ("&") in the URL.
> However, if I encode all ampersands as "&", I don't get the error
> and the viewer link shows up fine on the HTML page. I've been testing
> this in our 4.2 code but this particular piece of code doesn't
> appear to
> have changed since 4.1.
>
> Could you double check that you see this problem if all the ampersands
> in the URL are encoded as "&"?
>
> Thanks,
>
> Ethan
thredds archives: