[IDD #YBV-495737]: Fwd: No NDFD on CONDUIT

Hi Mike,

re:
> It sounds like it is the data vs. data2 issue, see below:

OK.

re:
> Our pattern looks like this:
> 
> REQUEST CONDUIT "^data/ndfd/.*[2]$” blizzard.rcac.purdue.edu
> 
> So it sounds like we just need to change data to data2 ?

My recommendation is to get rid if the 'data/' portion of the
extended regular expression entirely.  Here is an example:

REQUEST CONDUIT "ndfd/.*[2]$” blizzard.rcac.purdue.edu

You/your user can test the change using the LDM utility 'notifyme'
(by specifying the '-p <pattern>' flag to 'notifyme', or they can
just go for broke by making the change AND restarting their LDM.

re:
> Thanks!

No worries.  Sorry for the problem!

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: YBV-495737
Department: Support CONDUIT
Priority: Normal
Status: Closed