Hi Robert Thanks for the reply. I have resolved the issue. The problem was two folds. One the proper port on my firewall was not defined( $#$% for the firewall admin) and Two , yes there was this regex issue for sure.To achieve the desired effect i am now using simply sr2 in one backend while ^/sr2enotesheet in the other one. Works like a charm now. :)
Thank you for your support. Pound Team ROCKS!!!. One question When is the next version expected coz I could not locate the pound roadmap ? I am asking this as there are many forums which point me to Ngnix for similar requirements. Regards Dhiraj Gaur On Tue, Nov 17, 2009 at 10:34 PM, Robert Segall <[email protected]> wrote: > On Mon, 2009-11-16 at 14:14 +0530, Dhiraj Gaur wrote: > > Thanks Fabian for the reply. I ll re-describe the problem. > > > > Case 1 : When i have a URL "^/sr2" and URL "^/sr2enotesheet" for two diff > > backends, pound sends the requests meant > > sr2enotesheet to sr2 ie the URL matching is not effective and thus i get > a > > 404 error. > > > > case 2: When i have a URL "^/sr2/*" and URL "^/sr2enotesheet/*, in this > case > > the sr2 one works fine but I get an error as "Pound: no backend" for > > sr2enotesheet requests. > > I think you may want to read a bit about regular expressions. > > In your case "^/sr2" (as well as "^/sr2/*") will match > "^/sr2enotesheet". Since the first URL is specified before the second, > that is where your request will go (Pound does first match). > -- > Robert Segall > Apsis GmbH > Postfach, Uetikon am See, CH-8707 > Tel: +41-44-920 4904 > > > -- > To unsubscribe send an email with subject unsubscribe to [email protected]. > Please contact [email protected] for questions. > -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
