jruby-rack 1.1.9 → 1.1.10

Sign up to get free protection for your applications and to get access to all the features.
data/History.txt CHANGED
@@ -1,3 +1,12 @@
1
+ == 1.1.10 (04/09/12)
2
+
3
+ - correctly dechunk data from response and handle flushing,
4
+ finally Rails 3.1+ `render stream: true` support (#117)
5
+ - initial compatibility with Rails master (getting torwards 4.0.0.beta)
6
+ known issues: ActionController::Live seems to end up with a dead-lock
7
+ - ServletEnv now parses cookies using HttpServletRequest.getCookies instead of
8
+ leaving it off for Rack::Request
9
+
1
10
  == 1.1.9 (19/08/12)
2
11
 
3
12
  - rack env regression fix when used with rack-cache, introduced in 1.1.8 (#116)
data/README.md CHANGED
@@ -147,7 +147,7 @@ JRuby runtime management and pooling is done automatically by the framework.
147
147
  In the case of Rails, runtimes are pooled by default (the default will most
148
148
  likely change with the adoption of Rails 4.0). For other Rack applications a
149
149
  single shared runtime is created and shared for every request by default (as of
150
- **1.1.8** if *jruby.min.runtimes*/*jruby.max.runtimes* values are specified
150
+ **1.1.9** if *jruby.min.runtimes*/*jruby.max.runtimes* values are specified
151
151
  pooling is supported as well).
152
152
 
153
153
  ## JRuby-Rack Configuration
@@ -194,6 +194,11 @@ as context init parameters in web.xml or as VM-wide system properties.
194
194
  buffer, see also `jruby.rack.request.size.maximum.bytes` bellow.
195
195
  - `jruby.rack.request.size.maximum.bytes`: The maximum size for the request in
196
196
  memory buffer, if the body is larger than this it gets spooled to a tempfile.
197
+ - `jruby.rack.response.dechunk`: Set to false to turn off response dechunking
198
+ (Rails since 3.1 chunks response on `render stream: true`), it's on by default
199
+ as frameworks such as Rails might use `Rack::Chunked::Body` as a Rack response
200
+ body but since most servlet containers perform dechunking automatically things
201
+ might end double-chunked in such cases.
197
202
  - `jruby.rack.filter.adds.html`:
198
203
  **deprecated** use `addsHtmlToPathInfo` filter config init parameter.
199
204
  The default behavior for Rails and many other Ruby applications is to add an
@@ -7,6 +7,6 @@
7
7
 
8
8
  module JRuby
9
9
  module Rack
10
- VERSION = "1.1.9"
10
+ VERSION = "1.1.10"
11
11
  end
12
12
  end
metadata CHANGED
@@ -2,7 +2,7 @@
2
2
  name: jruby-rack
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: 1.1.9
5
+ version: 1.1.10
6
6
  platform: ruby
7
7
  authors:
8
8
  - Nick Sieger
@@ -10,7 +10,7 @@ autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
12
 
13
- date: 2012-08-19 00:00:00 Z
13
+ date: 2012-09-04 00:00:00 Z
14
14
  dependencies: []
15
15
 
16
16
  description: JRuby-Rack is a combined Java and Ruby library that adapts the Java Servlet API to Rack. For JRuby only.
@@ -26,8 +26,8 @@ files:
26
26
  - README.md
27
27
  - LICENSE.txt
28
28
  - History.txt
29
- - lib/jruby-rack-1.1.9.jar
30
29
  - lib/jruby-rack.rb
30
+ - lib/jruby-rack-1.1.10.jar
31
31
  - lib/jruby/rack/version.rb
32
32
  homepage: http://jruby.org
33
33
  licenses: []