I found similar problem when upgrading to Rails 1.2.6. Why did the change below work for you? I tried it without success. For some reason it only seems to be affecting one application, and the problem showed up after the log was rotated.
On Nov 18, 10:24 am, Chris Winslett <[EMAIL PROTECTED] s.net> wrote: > Changed line 105 of > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.13.5/lib/action_controller/request.rb > > from > > - ip =~ /^unknown$|^(10|172\.(1[6-9]|2[0-9]|30|31)|192\.168)\./i > + ip =~ /^unknown$|^(10|172\.(1[6-9]|2[0-9]|30|31))\./i > > > > Chris Winslett wrote: > > Does anyone know of a recent change in the way Rails or Mongrel handles > > headers? > > > After the following updates: > > > Rails updated to 1.2.5 > > Mongrel updated to 1.1 > > > All log files show as the following no matter the host they come from: > > > Processing UserController#login (for 127.0.0.1 at 2007-11-08 12:38:24) > > [GET] > > > The site runs throughApache2.2 load balancer, and no configuration > > changes have been made toApache. > > > Chris > > -- > Posted viahttp://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 -~----------~----~----~----~------~----~------~--~---
