Andre Arko 75dcdbc84e Restore original remote_ip algorithm. ... Proxy servers add X-Forwarded-For headers, resulting in a list of IPs. We remove trusted IP values, and then take the last given value, assuming that it is the most likely to be the correct, unfaked value. See [1] for a very thorough discussion of why that is the best option we have at the moment. [1]: http://blog.gingerlime.com/2012/rails-ip-spoofing-vulnerabilities-and-protection/ Fixes #7979		2013-01-02 15:26:27 -08:00
..
abstract	add tests to aliased _filter callbacks	2012-12-07 15:29:51 -05:00
activerecord	cleanup, remove trailing whitespace within actionpack	2012-10-27 16:03:18 +02:00
assertions	test response assertions	2012-01-06 11:20:26 -08:00
controller	do not append a second slash when using	2013-01-02 21:11:16 +01:00
dispatch	Restore original remote_ip algorithm.	2013-01-02 15:26:27 -08:00
fixtures	Digestor explicit dependency should not contain trailing whitespace	2012-12-21 18:00:51 -07:00
journey	Use ActiveSupport::TestCase in the journey tests	2012-12-31 14:40:43 -03:00
lib/controller	Add HTML5 input[type="color"] helper	2012-05-21 17:23:48 -03:00
routing	add some tests, yay!	2012-02-22 11:05:03 -08:00
template	No need to pass a empty block to content_tag_for anymore	2013-01-02 09:53:51 -03:00
tmp
abstract_unit.rb	Add active_support/testing/autorun	2012-12-31 13:57:24 -03:00
active_record_unit.rb	we're not supporting SQLite 2	2012-12-24 12:23:39 +09:00
ts_isolated.rb	Add active_support/testing/autorun	2012-12-31 13:57:24 -03:00