> @Simon: Yes used the manpage example initially but then I found that i
> need
> to map various different location servers on a single Public IP. Thus I
> have
> a rather long pound.cfg file. I am attaching the complete file for your
> reference
>
> Attaching error details
>
> On the browser I get the error
> "The service is not available. Please try again later."
>
> while in the syslog I get this error
> pound : no back-end "GET /sr2notesheet/ HTTP/1.0"

I hope that's a type        ^^^^^^^
Because you refer to "^/sr2enotesheet" in your config.

Simon

>
> Although I can browse the backend fine from the pound server web browser.
>
> I believe pound is getting confused between sr2 and sr2enotesheet.
>
> Regards
>
> Dhiraj gaur
>
> On Mon, Nov 16, 2009 at 1:38 PM, Dhiraj Gaur <[email protected]>
> wrote:
>
>> HI
>> I intially started off with a URL "^/sr2enotesheet" but then the tweaks
>> led
>> me to the current thing URL "^/sr2enotesheet\/*".
>> Both give me the same error. :(
>>
>> Regards
>> Dhiraj Gaur
>>
>> On Mon, Nov 16, 2009 at 1:26 PM, Simon Matter <[email protected]
>> >wrote:
>>
>> > > Hi all
>> > >
>> > > I have been using Pound in my setup for quite sometime now. I have
>> setup
>> > > various backends so that on the basis of URL request I can fetch
>> pages
>> > > from
>> > > various backend servers. For eg http://publicip/sr1 shall fetch page
>> > from
>> > > Location 1 while http://publicip/sr2 shall fetch pages from location
>> 2
>> > >
>> >
>> > Hi,
>> >
>> > I was just wondering about your URL directive and the one I'm using on
>> my
>> > own sites. Maybe I just didn't care enough but for the line you have
>> >
>> > URL "^/sr2enotesheet\/*"
>> >
>> > mine would look like
>> >
>> > URL "/sr2enotesheet/.*"
>> >
>> > Now I wondering why I'm not escaping / and why I'm not marking
>> beginning
>> > of the line with ^?
>> >
>> > Did you try the version used in the manpage, which mine is based on?
>> >
>> > Regards,
>> > Simon
>> >
>> >
>> > > Thus being on a single HTTP listener I can fetch pages from various
>> > > locations simply on the basis of URL.
>> > >
>> > > PROBLEM :
>> > > Now I have a request from one of my locations to add one more
>> backend.
>> > The
>> > > problem is the URL pattern. SR2 as a backend is already defined and
>> > > working.
>> > > When I add another backend with URL setting sr2email, POUND does not
>> seem
>> > > to
>> > > recognize the backend (even after service restart). and I see that
>> > > requests
>> > > somehow are queried on sr2 backend.
>> > >
>> > > The issue seems to go away when I rename sr2email to something other
>> than
>> > > which starts with sr2(say xyz)
>> > >
>> > > Plz help me where am I going wrong ???
>> > >
>> > > Pound.cfg:
>> > >
>> > >     Service "sr1"
>> > >         URL "^/sr1"
>> > >         BackEnd
>> > >             Address    192.168.14.26
>> > >             Port    80
>> > >         End
>> > >     End
>> > >
>> > >     Service "sr2enotesheet"
>> > >         URL "^/sr2enotesheet\/*"
>> > >         BackEnd
>> > >             Address    192.168.13.24
>> > >             Port 9009
>> > >         End
>> > >     End
>> > >
>> > >     Service "sr2"
>> > >         URL "^/sr2\/*"
>> > >         BackEnd
>> > >             Address    192.168.13.25
>> > >             Port    8008
>> > >         End
>> > >     End
>> > >
>> > >
>> > > Regards
>> > >
>> > > Dhiraj Gaur
>> > >
>> > >
>> > > --
>> > > 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.
>> >
>>
>>
>> --
>> 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.
>



--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to