On Sep 14, 5:15 pm, Alex Shulgin <alex.shul...@gmail.com> wrote: > > From what I can see, the problem has been noted in a more recent > version of Rails: > > https://github.com/rails/rails/blob/3-1-stable/actionpack/lib/action_... > > # TODO: Validate that the characters are UTF-8. If they aren't, > # you'll get a weird error down the road, but our form handling > # should really prevent that from happening > def encode_params(params) > > That's exactly what happens to us, and since the data isn't coming > from a webform we don't enjoy the mentioned form handling. > > I'd vote for a fix along the lines of Iconv.conv("#{$KCODE}//IGNORE", > $KCODE, ...), but I'm not sure what would be a good place to apply > that, more so that 2.3 and 3.x differ greatly in this regard, AFAICT.
I wonder if this will get more attention if I actually submit a patch... What would be the best place to apply the Iconv translation? I mean in the Rails world params are hashed already, so it might make sense to do this at some earlier stage, like in Rack? -- Alex -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
