This may be more of a question for a Rack list, as that's what's doing the parsing. However, I'd note that the only two incoming encodings that the parameter parser supports are application/x-www-form- urlencoded (which requires escaped semicolons) and multipart/form- data. You might have more luck getting ahold of the unparsed POST body from Rack::Request and handling it yourself.
--Matt Jones On Aug 13, 5:45 pm, "Florian j. Breunig" <rails-mailing-l...@andreas- s.net> wrote: > Hi, > > after upgrading Rails from 2.2.2 to 2.3.3 I realized that the handling > of request parameters has been changed regarding semicolons (that might > be due to the now integrated Rack interface). The following request > > curlhttp://127.0.0.1:3000/polls/initiate-d 'hallo=1;2' > > used to result in > > Parameters: {"hallo"=>"1;2"} > > in Rails 2.2.2. However, in Rails 2.3.3, the result is this: > > Parameters: {"hallo"=>"1", "2"=>nil} > > My application receives ICS (i.e. iCal) plain text containing semicolons > wrapped inside a POST request, so in my case a semicolon is *not* meant > to separate different parameters. How can I restore the previous > behaviour in Rails 2.3? > > Thank you > Flow > -- > Posted viahttp://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 [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 -~----------~----~----~----~------~----~------~--~---
