Joseph Wong 66dee26930 Fixed session ID fixation for ActiveRecord::SessionStore ... I have found that Rails will take an invalid session ID specified by the client and materialize a session based on that session ID. This means that it is possible, among other things, for a client to use an arbitrarily weak session ID or for a client to resurrect a previous used session ID. In other words, we cannot guarantee that all session IDs are generated by the server and that they are (statistically) unique through time. The fix is to always generate a new session ID in #get_session if an existing session cannot be found under the incoming session ID. Also added new tests that make sure that an invalid session ID is never materialized into a new session, regardless of whether it comes in via a cookie or a URL parameter (when :cookie_only => false).		2011-07-12 11:09:11 -07:00
..
active_record_store_test.rb	Fixed session ID fixation for ActiveRecord::SessionStore	2011-07-12 11:09:11 -07:00
controller_runtime_test.rb	Take into account time spent in AR even if a redirect occurs or if it is after the render	2011-05-23 10:58:43 +01:00
polymorphic_routes_test.rb	provide a more explicit message when using url_for with nil	2011-07-02 18:53:54 +02:00
render_partial_with_record_identification_test.rb	minor cleaning	2011-05-10 22:51:54 +05:30