You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few months ago I reported this issue against rack:
rack/rack#571 (gzip issue with jruby and Rack::ETag)
It seems the problem may be with the way jruby is implementing gzip compression, which apparently is is doing some strange reuse of objects internally.
The bug report above includes a test case to reproduce and some analysis by @srawlins
In short the problem appears to be that rack's etag handler is concatenating parts that are rightfully assumed to be immutable but that are actually being modified in jruby's gzip implementation. Since this seems to be a jruby bug, the issue was closed a few days on the rack side.
The text was updated successfully, but these errors were encountered:
A few months ago I reported this issue against rack:
rack/rack#571 (gzip issue with jruby and Rack::ETag)
It seems the problem may be with the way jruby is implementing gzip compression, which apparently is is doing some strange reuse of objects internally.
The bug report above includes a test case to reproduce and some analysis by @srawlins
In short the problem appears to be that rack's etag handler is concatenating parts that are rightfully assumed to be immutable but that are actually being modified in jruby's gzip implementation. Since this seems to be a jruby bug, the issue was closed a few days on the rack side.
The text was updated successfully, but these errors were encountered: