Hi,
   I dont have an answer to your quesion.  I just started trying to use 
the same document to serve multiple rails applications on Windows.

Page 5 of 13: Section - Link the configurations
Include conf/httpd-webbrick-proxy.conf

After adding this include line into the httpd.conf file, apache does not 
restart because it cannot load the httpd-webbrick-proxy.conf file. Do I 
have to download this file separately.  I do not see the 
httpd-webbrick-proxy.conf in the Apache2/conf directory.

I would appreciate any help.
Thanks
Udai

Kevin Ansberry wrote:
> I am attempting to follow the document created by Brain Hogan on
> "Serving Multiple Rails Applications on Windows with Apache and Mongrel"
> and all seems well except for one issue. One of my actions generates an
> xml document and uses the "send_data" method to return the file.
> However, this is the error I get when executing this controller action:
> 
> Proxy Error
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET
> /cbf_dev/admin/generate_spreadsheet_xml/2.
> 
> Reason: Error reading from remote server
> 
> 
> 
> This function works as expected when calling Mongrel directly, but as
> soon as I proxy the call through Apache to Mongrel, the above error.
> 
> Can anyone help me solve this issues? I think it is something to do with
> the way Apache (and the reverse_proxy_fix.rb file described in document
> mentioned above) is attempting to reconcile the name?
> 
> This newbie thanks you in advance for any help.
> 
> Kevin.


-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to