Rails / javascript：“太多参数键” - 规范化表单数据的好方法是什么？ [英] Rails / javascript: "too many parameter keys" - what's a good way to normalize form data?

问题描述

我正在使用导轨3.1.3。我有一个很多领域的表格。当表单提交时，我收到此错误

 错误RangeError：超过可用参数密钥空间
 / home / james /.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/utils.rb:99:in`block in parse_nested_query'
 /home/james/.rvm/ gems / ruby​​-1.9.3-p0 / gems / rack-1.3.6 / lib / rack / utils.rb：93：在`each'
 /home/james/.rvm/gems/ruby-1.9。 3-p0 / gems / rack-1.3.6 / lib / rack / utils.rb：93：在`parse_nested_query'
 /home/james/.rvm/gems/ruby-1.9.3-p0/gems/ rack-1.3.6 / lib / rack / request.rb：302：在`parse_query'
 /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/ lib / rack / request.rb：190：在`POST'
 /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/methodoverride。 rb：15：在`call'
 /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/runtime.rb:17:in`调用'
 /home/james/.rvm/gems/ruby-1.9.3-p0/gems/activesupport-3.1.3/lib/active_support/cache/strategy/local_cache.rb:72:in`call' 
 / home / jam在/ etc / /ruby-1.9.3-p0/gems/actionpack-3.1.3/lib/action_dispatch/middleware/static.rb:53:in`call'
 /home/james/.rvm/gems/ruby-1.9 .3-p0 / gems / railties-3.1.3 / lib / rails / engine.rb：456：在`call'
 /home/james/.rvm/gems/ruby-1.9.3-p0/gems $ / $ / $ / $ / $ $ / $ / $ .rb：59：在'service'
 /home/james/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/webrick/httpserver.rb:138:in`服务'
 /home/james/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/webrick/httpserver.rb:94:in`run'
 / home /詹姆斯/ .rvm /红宝石/红宝石1.9.3-P0 / LIB /红宝石/ 1.9.1 /的WEBrick / SERV er.rb：191：在'block in start_thread'
  

所以显然有太多的k / v正在提交的对。解决这个问题的好方法是什么？我以为我会拦截javascript的表单提交，然后以某种方式进行编码，以便只有一个k / v对，然后将其解码为应用服务器上的普通params哈希。任何这种方法的指导方针或更好的方法将不胜感激。

解决方案

这个问题是由Rack几个版本以前推出的。请参阅这些（ 1 ， 2 ）报告。
我通过将以下代码添加到初始化程序文件来解决问题。如果Rack :: Utils.respond_to？（key_space_limit =）
Rack :: Utils.key_space_limit = 262144，

 
 end 
  

I'm using rails 3.1.3. I have a form with a lot of fields. When the form is submitted, I get this error

ERROR RangeError: exceeded available parameter key space
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/utils.rb:99:in `block in parse_nested_query'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/utils.rb:93:in `each'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/utils.rb:93:in `parse_nested_query'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/request.rb:302:in `parse_query'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/request.rb:190:in `POST'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/methodoverride.rb:15:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/runtime.rb:17:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/activesupport-3.1.3/lib/active_support/cache/strategy/local_cache.rb:72:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/lock.rb:15:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/actionpack-3.1.3/lib/action_dispatch/middleware/static.rb:53:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/railties-3.1.3/lib/rails/engine.rb:456:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/content_length.rb:14:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/railties-3.1.3/lib/rails/rack/debugger.rb:21:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/railties-3.1.3/lib/rails/rack/log_tailer.rb:14:in `call'
    /home/james/.rvm/gems/ruby-1.9.3-p0/gems/rack-1.3.6/lib/rack/handler/webrick.rb:59:in `service'
    /home/james/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/webrick/httpserver.rb:138:in `service'
    /home/james/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/webrick/httpserver.rb:94:in `run'
    /home/james/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/webrick/server.rb:191:in `block in start_thread'

So apparently there are too many k/v pairs being submitted. What's a good way to get around this problem? I'm thinking that I'll intercept submission of the form with javascript, then encode it somehow so that there's only one k/v pair, then decode it to an ordinary params hash on the app server. Any guidelines for this approach, or a better approach would be appreciated.

解决方案

This issue was introduced by Rack few releases ago. Refer to these (1, 2) reports. I addressed the issue by adding the following code to initializer file.

if Rack::Utils.respond_to?("key_space_limit=")
  Rack::Utils.key_space_limit = 262144 
end

这篇关于Rails / javascript：“太多参数键” - 规范化表单数据的好方法是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！