Hi Kristian, this also results in port number '3000', and not in the port number of the upstream mongrel.
On 9 Dez., 09:46, Kristian Hellquist <[email protected]> wrote: > Cant you just do `request.server_port' in controller? > > 2009/12/9 Thomas <[email protected]>: > > > > > For debugging purpose I find it helpful to see which mongrel out of an > > upstream cluster, specifically which port number, handles an actual > > request. For example, let the load balancer operate on port 3000 > > (development) and the upstream mongrel cluster operating on ports 4000 > > upto 4002, then I would like to see not only the port 3000 (eg. using > > request.host_with_port in a controller) but also the port number of > > the actual mongrel instance. > > > With Rails 2.1 I used session.cgi to spot the mongrel port (4000, 4001 > > or 4002), however, I was not able to figure this out in Rails 2.3 > > which is using the rack middleware. > > > Any idea, how to do it? > > > Greetings and thanks! > > Thomas > > > -- > > > 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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/rubyonrails-talk?hl=en. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
