Aaron Patterson 24f9c03d52 Revert "removing Rack::Runtime from the default stack." ... This reverts commit 37423e4ff8. Jeremy is right that we shouldn't remove this. The fact is that many engines are depending on this middleware to be in the default stack. This ties our hands and forces us to keep the middleware in the stack so that engines will work. To be extremely clear, I think this is another smell of "the rack stack" that we have in place. When manipulating middleware, we should have meaningful names for places in the req / res lifecycle **not** have engines depend on a particular constant be in a particular place in the stack. This is a weakness of the API that we have to figure out a way to address before removing the constant. As far as timing attacks are concerned, we can reduce the granularity such that it isn't useful information for hackers, but is still useful for developers.		2015-10-03 14:21:31 -07:00
..
bootstrap.rb	Revert "removing Rack::Runtime from the default stack."	2015-10-03 14:21:31 -07:00
configuration.rb	Stop modifying global variables	2015-09-29 14:03:09 -04:00
default_middleware_stack.rb	Revert "removing Rack::Runtime from the default stack."	2015-10-03 14:21:31 -07:00
finisher.rb	We need stricter locking before we can unload	2015-07-20 09:14:10 +09:30
routes_reloader.rb	Pass symbol as an argument instead of a block	2014-11-29 11:53:24 +01:00