Both of those URLs would match. Are you sure you're not seeing some other behavior? (i.e. URL with no-slash would cause a normal webserver like apache to send a redirect, which may or may not succeed depending on your redirect rewrite settings... But that wouldn't be a problem with your URL matching.)
Joe > -----Original Message----- > From: Andreas H. [mailto:[email protected]] > Sent: Sunday, January 01, 2012 12:28 PM > To: [email protected] > Subject: [Pound Mailing List] Matching URL pattern in Service > definition > > Hi, > > this is probably a very noob question, but I cannot seem to get it > right: > > I'm wondering why in a service defined as > > Service > URL "^/atmdoc" > Session > Type IP > TTL 300 > End > BackEnd > Address 10.0.10.66 > Port 80 > End > End > > the URL "http://www.myserver.com/atmdoc/"; does match, but without the > trailing slash, "http://www.myserver.com/atmdoc";, the service pattern > does not seem to match. > > So how should I form the pattern to match also without the trailing > slash? > > Cheers, > Andreas. > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. N�����r��zǧu�ޙ���+a���y�n�˛���m�h���u�l��!>W���(�֜��,z��+ ��+�笶*'
