jruby-rack
jruby-rack copied to clipboard
Rack for JRuby and Java appservers
http://stackoverflow.com/questions/3027564/can-i-have-sinatra-rack-not-read-the-entire-request-body-into-memory ... inspired by https://github.com/nandosola/trantor-stream-uploader
JRubyJars.jruby_rack_jar_path will return the exact jar path, including version numbers. If you use this path in the MANIFEST.MF Class-Path directive, you'll create a dependency on that version of the JRubyRack...
I was very pleasantly surprised to see this project place so well here: http://www.techempower.com/benchmarks/#section=data-r8&hw=i7&test=json It's about time we see a project like this ticking up into the respectable region!
Bumps [rack](https://github.com/rack/rack) from 1.2.1 to 2.2.8.1. Release notes Sourced from rack's releases. v2.2.8.1 What's Changed Fixed ReDoS in Accept header parsing [CVE-2024-26146] Fixed ReDoS in Content Type header parsing [CVE-2024-25126]...
Bumps [rack](https://github.com/rack/rack) from 1.3.3 to 3.0.9.1. Release notes Sourced from rack's releases. v3.0.9.1 What's Changed Fixed ReDoS in Accept header parsing [CVE-2024-26146] Fixed ReDoS in Content Type header parsing [CVE-2024-25126]...
I don't really have any deep experience with Rack or JRuby Rack - so please excuse the question if it speaks to ignorance. After upgrading a JRuby-on-Rails application from Rails...
This is work-in-progress to get the tests running/passing again against latest JRuby. - [x] Resolve the issue in https://github.com/jruby/jruby-rack/commit/477502ce032107f46110d192b10adc3869d3b6d1 - Root problem seems to be that running the Rake `ruby`...
I am not sure if Logger is always loaded or not. With rails app it seems it is.
jruby-rack `1.2.x` seems to barf while running on app that was previously working fine with - Java `21` - JRuby `9.4.7.0` - Rails `6.1` w/ Sprockets `4.2.1` and Rack `2.2.9`...
These are not all green but it's better to have them running than not.