Cordova App on Android using SSL sending multipart/form-data causes Rack app error: #<EOFError: bad content body>
Cordova App on Android using SSL sending multipart/form-data causes Rack app error: #<EOFError: bad content body>
我们有一个通过 SSL 连接到 rails 服务器的 Cordova 应用程序。我们最近从 Unicorn 到 Puma 的更改似乎导致 Android 应用程序在向服务器发送图像文件时出现 500 错误。
一些注意事项：
- 应用程序的 iOS 版本使用完全相同的代码构建，运行良好
- 如果不使用 SSL，一切正常
- 所有其他请求都是 SSL 并且工作正常，只有在发送
multipart/form-data 这个问题令人讨厌。
我正在努力思考问题可能是什么，甚至不知道去哪里寻找解决方案。我对 Puma 很陌生，所以我不知道我的配置中是否遗漏了一些重要的东西来处理这个问题。任何想法将不胜感激。
iOS 请求（工作正常）
POST /api/v2/attachments HTTP/1.1
Host: <omitted for security>
Accept: */*
Proxy-Connection: keep-alive
X-Requested-With: XMLHttpRequest
Accept-Encoding: gzip, deflate
If-None-Match: "2146f2b315668b29682ec01973ae4155"
Accept-Language: en-us
Content-Type: multipart/form-data; boundary=+++++org.apache.cordova.formBoundary
Content-Length: 13794
User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Mobile/13B143 (4954749952)
Connection: keep-alive
Cookie: XSRF-TOKEN=<omitted for security>; _session_id=<omitted for security>
--+++++org.apache.cordova.formBoundary
Content-Disposition: form-data; name="type"
Image
--+++++org.apache.cordova.formBoundary
Content-Disposition: form-data; name="attachment[attachment]"; filename="cdv_photo_003.jpg"
Content-Type: image/jpeg
Content-Length: 13466
iُ B~,"
#BRbr
%&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
B #3Rbr
%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
""""""''''',,,,,,,,,,
...................................................(<a$GW_ЬUպi&dA+x=R
?)uHv"ԊdcpIސW̚<<Kx~E1xEN]M%>r{Y_Yc<jʥYH_2r[P['6 d#wS+5Bfu
<more Binary data omitted for brevity>
--+++++org.apache.cordova.formBoundary--
等效Android请求（导致错误）
POST /api/v2/attachments HTTP/1.1
Content-Type: multipart/form-data; boundary=+++++
Cookie: _session_id=<omitted for security>; XSRF-TOKEN=<omitted for security>
Transfer-Encoding: chunked
User-Agent: Dalvik/2.1.0 (Linux; U; Android 5.0; SM-G900F Build/LRX21T)
Host: <omitted for security>
Connection: Keep-Alive
Accept-Encoding: gzip
--+++++
Content-Disposition: form-data; name="type"
Image
--+++++
Content-Disposition: form-data; name="attachment[attachment]"; filename="modified.jpg?1446611766814"
Content-Type: image/jpeg
Exif
(1#%(:3=<9387@H\N@DWE78PmQW_bghg>Mqypdx\egc"
#BRbr
<more Binary data omitted for brevity>
--+++++--
这些请求之间存在一些明显的差异，虽然我不会称自己为 HTTP 协议专家，但 none 的差异在我看来可能会导致 Puma 崩溃。
机架错误跟踪：
2015-11-04T04:36:07.041124+00:00 app[web.1]: 2015-11-04 04:36:07 +0000: Rack app error: #<EOFError: bad content body>
2015-11-04T04:36:07.041131+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:74:in `block in fast_forward_to_first_boundary'
2015-11-04T04:36:07.041133+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:72:in `loop'
2015-11-04T04:36:07.041134+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:72:in `fast_forward_to_first_boundary'
2015-11-04T04:36:07.041152+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:15:in `parse'
2015-11-04T04:36:07.041153+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart.rb:25:in `parse_multipart'
2015-11-04T04:36:07.041154+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/request.rb:377:in `parse_multipart'
2015-11-04T04:36:07.041154+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/request.rb:203:in `POST'
2015-11-04T04:36:07.041155+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:26:in `method_override'
2015-11-04T04:36:07.041156+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:14:in `call'
2015-11-04T04:36:07.041157+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041157+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
2015-11-04T04:36:07.041158+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041158+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-rewrite-1.5.0/lib/rack/rewrite.rb:24:in `call'
2015-11-04T04:36:07.041159+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041159+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.5/lib/active_support/cache/strategy/local_cache.rb:83:in `call'
2015-11-04T04:36:07.041160+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041160+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/actionpack-4.0.5/lib/action_dispatch/middleware/static.rb:64:in `call'
2015-11-04T04:36:07.041161+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041161+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
2015-11-04T04:36:07.041161+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041162+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/railties-4.0.5/lib/rails/engine.rb:511:in `call'
2015-11-04T04:36:07.041162+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/railties-4.0.5/lib/rails/application.rb:97:in `call'
2015-11-04T04:36:07.041163+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/railties-4.0.5/lib/rails/railtie/configurable.rb:30:in `method_missing'
2015-11-04T04:36:07.041163+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041163+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/configuration.rb:78:in `call'
2015-11-04T04:36:07.041164+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/server.rb:541:in `handle_request'
2015-11-04T04:36:07.041164+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/server.rb:388:in `process_client'
2015-11-04T04:36:07.041165+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/server.rb:270:in `block in run'
2015-11-04T04:36:07.041165+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/thread_pool.rb:106:in `call'
2015-11-04T04:36:07.041165+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/thread_pool.rb:106:in `block in spawn_thread'
2015-11-04T04:36:07.523877+00:00 heroku[router]: sock=backend at=error code=H18 desc="Server Request Interrupted" method=POST path="/api/v2/attachments" host=<omitted for security> request_id=a5958dab-8c7c-4121-acc3-54d28be9ad4c fwd="<omitted for security>" dyno=web.1 connect=2ms service=484ms status=503 bytes=154
您应该检查服务器日志中关于此 500 错误的内容
你应该猴子补丁 Rack::Multipart::Parser.fast_forward_to_first_boundary 添加日志跟踪并确认传递给解析器的内容在到达该函数时为空（即 StringIO 引用的 [=12] =] 在多部分解析期间 returns 无数据）。
更多信息：rack-throwing-eoferror-bad-content-body
我未能圆满解决此问题，问题的根源似乎是 Puma 处理 multipart/chunked 数据的方式。由于我们使用的不是最新版本，此时升级也不容易，所以我'hacked'有如下解决方案。
奇怪的是，似乎是缺失的 Content-Length header 导致了这个问题 - 尽管 HTTP 规范规定分块请求不应该有这个 header.
我认为（尽管我可能是错的）SSL 实现需要 Content-Length，这与不提供分块请求的要求不一致。
目前的解决方案是从 cordova 应用程序中禁用分块数据。我们正在使用 cordova-file-transfer-plugin，它允许我们将 chunked 设置为 false。
不理想，但确实有效。
来自 https://github.com/apache/cordova-plugin-file-transfer
options.chunkedMode = false;
我们有一个通过 SSL 连接到 rails 服务器的 Cordova 应用程序。我们最近从 Unicorn 到 Puma 的更改似乎导致 Android 应用程序在向服务器发送图像文件时出现 500 错误。
一些注意事项：
- 应用程序的 iOS 版本使用完全相同的代码构建，运行良好
- 如果不使用 SSL，一切正常
- 所有其他请求都是 SSL 并且工作正常，只有在发送 multipart/form-data 这个问题令人讨厌。
我正在努力思考问题可能是什么，甚至不知道去哪里寻找解决方案。我对 Puma 很陌生，所以我不知道我的配置中是否遗漏了一些重要的东西来处理这个问题。任何想法将不胜感激。
iOS 请求（工作正常）
POST /api/v2/attachments HTTP/1.1
Host: <omitted for security>
Accept: */*
Proxy-Connection: keep-alive
X-Requested-With: XMLHttpRequest
Accept-Encoding: gzip, deflate
If-None-Match: "2146f2b315668b29682ec01973ae4155"
Accept-Language: en-us
Content-Type: multipart/form-data; boundary=+++++org.apache.cordova.formBoundary
Content-Length: 13794
User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Mobile/13B143 (4954749952)
Connection: keep-alive
Cookie: XSRF-TOKEN=<omitted for security>; _session_id=<omitted for security>
--+++++org.apache.cordova.formBoundary
Content-Disposition: form-data; name="type"
Image
--+++++org.apache.cordova.formBoundary
Content-Disposition: form-data; name="attachment[attachment]"; filename="cdv_photo_003.jpg"
Content-Type: image/jpeg
Content-Length: 13466
iُ B~,"
#BRbr
%&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
B #3Rbr
%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
""""""''''',,,,,,,,,,
...................................................(<a$GW_ЬUպi&dA+x=R
?)uHv"ԊdcpIސW̚<<Kx~E1xEN]M%>r{Y_Yc<jʥYH_2r[P['6 d#wS+5Bfu
<more Binary data omitted for brevity>
--+++++org.apache.cordova.formBoundary--
等效Android请求（导致错误）
POST /api/v2/attachments HTTP/1.1
Content-Type: multipart/form-data; boundary=+++++
Cookie: _session_id=<omitted for security>; XSRF-TOKEN=<omitted for security>
Transfer-Encoding: chunked
User-Agent: Dalvik/2.1.0 (Linux; U; Android 5.0; SM-G900F Build/LRX21T)
Host: <omitted for security>
Connection: Keep-Alive
Accept-Encoding: gzip
--+++++
Content-Disposition: form-data; name="type"
Image
--+++++
Content-Disposition: form-data; name="attachment[attachment]"; filename="modified.jpg?1446611766814"
Content-Type: image/jpeg
Exif
(1#%(:3=<9387@H\N@DWE78PmQW_bghg>Mqypdx\egc"
#BRbr
<more Binary data omitted for brevity>
--+++++--
这些请求之间存在一些明显的差异，虽然我不会称自己为 HTTP 协议专家，但 none 的差异在我看来可能会导致 Puma 崩溃。
机架错误跟踪：
2015-11-04T04:36:07.041124+00:00 app[web.1]: 2015-11-04 04:36:07 +0000: Rack app error: #<EOFError: bad content body>
2015-11-04T04:36:07.041131+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:74:in `block in fast_forward_to_first_boundary'
2015-11-04T04:36:07.041133+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:72:in `loop'
2015-11-04T04:36:07.041134+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:72:in `fast_forward_to_first_boundary'
2015-11-04T04:36:07.041152+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart/parser.rb:15:in `parse'
2015-11-04T04:36:07.041153+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/multipart.rb:25:in `parse_multipart'
2015-11-04T04:36:07.041154+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/request.rb:377:in `parse_multipart'
2015-11-04T04:36:07.041154+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/request.rb:203:in `POST'
2015-11-04T04:36:07.041155+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:26:in `method_override'
2015-11-04T04:36:07.041156+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:14:in `call'
2015-11-04T04:36:07.041157+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041157+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
2015-11-04T04:36:07.041158+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041158+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-rewrite-1.5.0/lib/rack/rewrite.rb:24:in `call'
2015-11-04T04:36:07.041159+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041159+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/activesupport-4.0.5/lib/active_support/cache/strategy/local_cache.rb:83:in `call'
2015-11-04T04:36:07.041160+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041160+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/actionpack-4.0.5/lib/action_dispatch/middleware/static.rb:64:in `call'
2015-11-04T04:36:07.041161+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041161+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
2015-11-04T04:36:07.041161+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041162+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/railties-4.0.5/lib/rails/engine.rb:511:in `call'
2015-11-04T04:36:07.041162+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/railties-4.0.5/lib/rails/application.rb:97:in `call'
2015-11-04T04:36:07.041163+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/railties-4.0.5/lib/rails/railtie/configurable.rb:30:in `method_missing'
2015-11-04T04:36:07.041163+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/newrelic_rpm-3.13.2.302/lib/new_relic/agent/instrumentation/middleware_tracing.rb:67:in `call'
2015-11-04T04:36:07.041163+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/configuration.rb:78:in `call'
2015-11-04T04:36:07.041164+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/server.rb:541:in `handle_request'
2015-11-04T04:36:07.041164+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/server.rb:388:in `process_client'
2015-11-04T04:36:07.041165+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/server.rb:270:in `block in run'
2015-11-04T04:36:07.041165+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/thread_pool.rb:106:in `call'
2015-11-04T04:36:07.041165+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/thread_pool.rb:106:in `block in spawn_thread'
2015-11-04T04:36:07.523877+00:00 heroku[router]: sock=backend at=error code=H18 desc="Server Request Interrupted" method=POST path="/api/v2/attachments" host=<omitted for security> request_id=a5958dab-8c7c-4121-acc3-54d28be9ad4c fwd="<omitted for security>" dyno=web.1 connect=2ms service=484ms status=503 bytes=154
您应该检查服务器日志中关于此 500 错误的内容
你应该猴子补丁 Rack::Multipart::Parser.fast_forward_to_first_boundary 添加日志跟踪并确认传递给解析器的内容在到达该函数时为空（即 StringIO 引用的 [=12] =] 在多部分解析期间 returns 无数据）。
更多信息：rack-throwing-eoferror-bad-content-body
我未能圆满解决此问题，问题的根源似乎是 Puma 处理 multipart/chunked 数据的方式。由于我们使用的不是最新版本，此时升级也不容易，所以我'hacked'有如下解决方案。
奇怪的是，似乎是缺失的 Content-Length header 导致了这个问题 - 尽管 HTTP 规范规定分块请求不应该有这个 header.
我认为（尽管我可能是错的）SSL 实现需要 Content-Length，这与不提供分块请求的要求不一致。
目前的解决方案是从 cordova 应用程序中禁用分块数据。我们正在使用 cordova-file-transfer-plugin，它允许我们将 chunked 设置为 false。
不理想，但确实有效。 来自 https://github.com/apache/cordova-plugin-file-transfer
options.chunkedMode = false;