Hi - I just installed Pound and its working well with virtual hosts,
however, i'm planning to have a single domain which will redirect based from
the URL it matches and it will redirect to backend server with its full URL
and not just the server and port number.

I was able to do the below sample using apache + mod_proxy but not sure if
Pound can do that as well.

e.g.

www.mydomain.com/wiki should redirect and serve the content from
http://192.168.1.10:8080/wiki/index.php

www.mydomain.com/exchange should redirect to http://192.168.1.11/exchange

www.mydomain.com/myapp should redirect to
http://192.168.1.11/mynewapp/index.aspx

is it possible? if yes, can you help me with the config?

Regards'

zham

zham rock wrote:[...]

Definitely possible.  You'll want to setup multiple 'Service' sections 
in your config for each url that you want mapped in some way.  So, roughly:

ListenHTTP
	Address a.b.c.d
	Port 80

	Service "wiki"
		URL "^/wiki"
		Backend
			....
		End
	end
	Service "exchange"
		URL "^/exchange"
		Backend
			...
		end
	end
	...
end

Just add as many service directives as you want.  Be sure to add one w/o 
any 'URL' keyword to act as a default.  The checks are made with a 
first-match policy, so order matters.

Regards,[...]

Thanks - but how can i configure the backend? e.g. how do i make sure it
goes to my backend http://192.168.1.11/wiki
<http://192.168.1.11/exchange>and
not to
http://192.168.1.11/exchange



On Fri, May 30, 2008 at 2:08 AM, Dave Steinberg <dave(at)redterror.net>
wrote:
[...][...][...]

zham rock wrote:[...]

In pound, each service section has its own backend definitions.  So if 
you want /wiki to go to 192.168.1.11, just define that backend in your 
service section:

Service
...
	URL "^/wiki"
	Backend
		Address 192.168.1.11
		Port 80
	End
end

Do that for each url you want to have special treatment.  Note that 
pound does not strip the path of the url, so in the above 192.168.1.11 
would see a request for "/wiki".

Why don't you try making a config and testing it to get a handle on the 
behavior?  Then we can talk about what didn't work that you expected to 
go another way based on your config.

Regards,[...]

I apologies if i did not make myself clear.

I have a multiple .Net applications hosted on a single IIS web server.

e.g.

i want to make sure that

http://www.mydomain.com/myapp1
should redirect to http://192.168.1.11/myapp1
http://www.mydomain.com/myapp2
should redirect to http://192.168.1.11/myapp2
http://www.mydomain.com/myapp3
should redirect to http://192.168.1.11/myapp3

Did that make sense? is that possible in pound?

Regards'

-zham
On Fri, May 30, 2008 at 8:47 PM, Dave Steinberg <dave(at)redterror.net>
wrote:
[...][...][...]

Hi Guys - can somebody tell if this is feasible?

Regards'

zham

On Sat, May 31, 2008 at 8:27 PM, zham rock <zhamrock(at)gmail.com> wrote:
[...]

Yes, it is.  Refer back in the archive a days, somebody already 
explained how to do it.

zham rock wrote:[...][...]
>>> zham rock wrote:
>>>
>>>       
>>>> Thanks - but how can i configure the backend? e.g. how do i
make sure it
>>>> goes to my backend http://192.168.1.11/wiki
>>>> <http://192.168.1.11/exchange>and
not to
>>>> http://192.168.1.11/exchange
>>>>
>>>>         
>>> In pound, each service section has its own backend definitions. 
So if
>>>       [...]
>>> want /wiki to go to 192.168.1.11, just define that backend in your
>>>       [...]
>>> section:
>>>
>>> Service
>>> ...
>>>        URL "^/wiki"
>>>        Backend
>>>                Address 192.168.1.11
>>>                Port 80
>>>        End
>>> end
>>>
>>> Do that for each url you want to have special treatment.  Note
that pound
>>> does not strip the path of the url, so in the above 192.168.1.11
would
>>>       [...]
>>> a request for "/wiki".
>>>
>>> Why don't you try making a config and testing it to get a handle
on the
>>> behavior?  Then we can talk about what didn't work that you
expected to
>>>       [...]
>>> another way based on your config.
>>>
>>>
>>> Regards,
>>> --
>>> Dave Steinberg
>>> http://www.geekisp.com/
>>> http://www.steinbergcomputing.com/
>>>
>>> --
>>> To unsubscribe send an email with subject unsubscribe to
pound(at)apsis.ch.
>>> Please contact roseg(at)apsis.ch for questions.
>>>
>>>       [...][...]

> Hi Guys - can somebody tell if this is feasible?

If I understand you correctly I think something like this should do it for
myapp1. Add more services accordingly. That way you could even send
requests for myapp2+3 to different backend servers if you like.

Service
    Url         "/myapp1/.*"
    HeadRequire "Host:.*www.mydomain.com.*"
    BackEnd
        Address 192.168.1.11
        Port    80
        TimeOut 300
    End
End

Maybe you want to try

Url         "/myapp.*"

so that you need only ony service entry for all threee services.

Simon
[...][...][...]