I dont know much about HeadRequire but I presume it is very strict and redirects according to the host header ...

As far as URL I think its more flexible and can be used generically i.e.


Service
 Url         ".*/cgi-bin/script.cgi(%4.*|%5.*|\[.*|\]|%3.*|%2.*|%0.*)"
 BackEnd
    Address  127.0.0.1
     Port  81
 End
End

This means
http://domain1.com/cgi-bin/script.cgi.Any thing else with funny chars like those accept
http://domain2.com/cgi-bin/script.cgi.Any thing else with funny chars like those accept

etc etc
I can keep adding urls or even more specific urls dedicated to a domain and funny chars or ,* which is all and send it to a backend....

Then to wrap it all up a thing to catch any dodgy chars for urls that you know wont require any funny chars which is the rest of the site

Service
 Url         ".*.(%.*|\[|\]|`|;|\|@|\||~|<|>|\"|\$|\(|\)|\{|\}|\*|!|')"
 Redirect    "http://www.masterdomain.com/"
   BackEnd
     Address  127.0.0.1
     Port  81
   End

End

#and finally to send all good traffic to the right host

Service
  BackEnd
    Address  127.0.0.1
    Port  81
  End
End


And there you have it

In basic Url can be used for looking a pattern across multiple sites and doing a redirect according to that..


I need to get a job at pound hehe dont worry am a nubee tooo at this but is very cool

Peace to all the pounders

Keep pounding away





On 19/09/2007, Pete DeLaurentis <pete@nextengine.com> wrote:
Thanks for the help guys.

I had a question if there was any difference between the virtual
hosting method, where you use:

HeadRequire "Host: .*monkey.nextengine.com.*"

Or the URL method mentioned by Mister V:

Url         "monkey.nextengine.com.*"

In my limited understanding the chief disadvantage of virtual hosts
is that they don't work through SSL.  Are both of these methods
"virtual hosting"?

Thanks,
Pete


> Dave Steinberg wrote:
>>> Does anyone know how to route based on subdomain specified in the
>>> URL?
>>>
>>> I have two subdomains pointing to one server running pound as a
>>> load balancer (155.132.55.32).  The load balancer also functions
>>> as a development test server box.
>>>
>>> Here's the desired mapping:
>>>
>>> monkey.nextengine.com   => 155.132.55.32
>>> elephant.nextengine.com   => 155.132.55.34, 155.132.55.35
>>
>> Follow the example labeled 'VIRTUAL HOSTS (IN GENERAL)' on the
>> pound homepage:
>>
>> http://www.apsis.ch/pound
>>
>> That's how I do it for a number of sites.  Despite being not
>> recommended, it works great!
>>
>> PS - Anyone know why it isn't recommended?
> The author of the pound page gives two reasons - go back and read
> more carefully the part about vhosts!
> Alex
>
>
>>
>> Regards,
>
>
>
> --
> To unsubscribe send an email with subject unsubscribe to
> pound@apsis.ch.
> Please contact roseg@apsis.ch for questions.


--
To unsubscribe send an email with subject unsubscribe to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.