It is really easier than Apache that is why it seems so hard.  :-)
When you first create the rule, it asks you for the URL.  What did you
put in there?  If my vhost or default host is http://mysite.com.  I
have one default rule.

Lets try it this way.  Do you only have one rule you will be using for
this vhost?

On Mon, Mar 7, 2011 at 4:39 PM, Ghent <[email protected]> wrote:
> Tony,
>
> I'm afraid I don't follow?  I'm an apache wiz and I have to say, all
> this is leaving me feeling quite stupid lol ;)
>
>
>
> On Mon, Mar 7, 2011 at 4:32 PM, Tony Zakula <[email protected]> wrote:
>> Ah!  Maybe that is your issue.  Your URL for your rule is usually
>> something like "/blog" meaning the request is coming in to your vhost,
>> and it is matching off of the root.  Does that make sense?  So if your
>> vhost URL is http://lbbrf.griefwatch.net, you could just use "/".
>>
>> On Mon, Mar 7, 2011 at 4:26 PM, Ghent <[email protected]> wrote:
>>> Tony,
>>>
>>> Thank you.  I tried what I think your answers are saying but I had
>>> different trouble.
>>>
>>>>> 1) In Cherokee I setup a new information source as an external site
>>>>> with the address being "lbbrf.griefwatch.net"
>>>>
>>>> - I am assuming this is setup as http://lbbrf.griefwatch.net
>>>>
>>>
>>> I changed my information source from 'lbbrf.griefwatch.net' to
>>> 'http://lbbrf.griefwatch.net'.  When I made this change, I started to
>>> get a 503 service unavailable message from the browser when trying to
>>> access my reverse proxy URL (http://www.lbbrf.com/kb/)
>>>
>>>
>>>> 2) In my vhost I created a directory with a Reverse Proxy handler
>>>> 2a) The only option enabled is use keep-alives
>>>>
>>>> - You probably want to enable preserve host header.  This makes a
>>>> difference if you are going in and coming back out.
>>>>
>>>
>>> I turned on Enable Preserve Host Header (it was previously off)
>>>
>>>
>>>> 2b) The information source is set to my configured information source
>>>>
>>>> Check that and let us know.
>>>>
>>>
>>> Not sure what you meant by this.  I checked that it was configured to
>>> use my information source, which is mentioned above.  Its set to use
>>> round robin with the only defined source being the source above.
>>>
>>> With the source being configured as 'lbbrf.griefwatch.net' the proxy
>>> address ends up redirecting to the main website of the host I am
>>> trying to proxy.  You can see this behavior right now if you go to
>>> http://www.lbbrf.com/kb/
>>>
>>> With the source being configured as 'http://griefwatch.net' the proxy
>>> address returns a "503 service unavailable" error.
>>>
>>> Anything further we could try?  Or perhaps more detailed information?
>>> Thank you.
>>>
>>>  .: Ghent
>>>
>>
>
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to