Our current deployment is under Apache 1.3 via FastCGI, but we''re thinking of moving to the current deployment of choice - Apache 2.0, mod_proxy_balancer and a Mongrel cluster. Unfortunately we have hit a problem with ActionWebService. Are we missing something? The problem is that the WSDL file automatically generated by ActionWebService points at the cluster, rather than the Apache 2.0 proxy. Instead of: <soap:address location="http://mydomain.com/my_service/api" /> it contains: <soap:address location="http://localhost:3002/my_service/api" /> As far as we can tell, instead of using request.host (which examines HTTP_X_FORWARDED_HOST), ActiveWebService uses HTTP_HOST directly. Are we missing something? Has anyone else used ActiveWebService in an Apache 2.0/Mongrel deployment? Thanks in advance, paul.butcher->msgCount++ -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 8/30/06, Paul Butcher <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > Our current deployment is under Apache 1.3 via FastCGI, but we''re > thinking of moving to the current deployment of choice - Apache 2.0, > mod_proxy_balancer and a Mongrel cluster. Unfortunately we have hit a > problem with ActionWebService. Are we missing something? > > The problem is that the WSDL file automatically generated by > ActionWebService points at the cluster, rather than the Apache 2.0 > proxy. Instead of: > > <soap:address location="http://mydomain.com/my_service/api" /> > > it contains: > > <soap:address location="http://localhost:3002/my_service/api" /> > > As far as we can tell, instead of using request.host (which examines > HTTP_X_FORWARDED_HOST), ActiveWebService uses HTTP_HOST directly. Are we > missing something? Has anyone else used ActiveWebService in an Apache > 2.0/Mongrel deployment? >This is a bug in AWS. Please submit a ticket. -- Kent --- http://www.datanoise.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Kent Sibilev wrote:> This is a bug in AWS. Please submit a ticket.Done <http://dev.rubyonrails.org/ticket/5996> I''m working on a patch and will update the ticket when I''ve done so. Given the popularity of the Apache 2.0, mod_proxy_balancer and Mongrel deployment, I''m kinda amazed that we seem to be the first people to hit this problem. Ah well... paul.butcher->msgCount++ -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 8/31/06, Paul Butcher <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > Given the popularity of the Apache 2.0, mod_proxy_balancer and Mongrel > deploymentCompletely off topic, but I think you mean Apache *2.2*, mod_proxy_balancer and Mongrel. AFAIK, mod_proxy_balancer won''t work with 2.0. Isak --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Isak Hansen wrote:> Completely off topic, but I think you mean Apache *2.2*, > mod_proxy_balancer and Mongrel. AFAIK, mod_proxy_balancer won''t work > with 2.0.You are, of course, entirely correct. Thanks, paul.butcher->msgCount++ -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Paul Butcher wrote:> Kent Sibilev wrote: >> This is a bug in AWS. Please submit a ticket. > > Done <http://dev.rubyonrails.org/ticket/5996> > > I''m working on a patch and will update the ticket when I''ve done so.Patch attached. paul.butcher->msgCount++ -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Isak Hansen wrote:> On 8/31/06, Paul Butcher <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote: >> >> Given the popularity of the Apache 2.0, mod_proxy_balancer and Mongrel >> deployment > > Completely off topic, but I think you mean Apache *2.2*, > mod_proxy_balancer and Mongrel. AFAIK, mod_proxy_balancer won''t work > with 2.0.Staying off-topic, I think the reason is the *lack* of popularity for ActionWebService. No insult intended. It''s not quite deprecated, but it has been discouraged. Bleeding Edgers are likely to be the ones on the hot new deployment setup, and Bleeding Edgers are likely to be the ones ditching AWS for simply_restful and/or ActiveResource, I guess. Alan -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---