aboutsummaryrefslogtreecommitdiffstats
path: root/railties/doc/guides/actioncontroller/parameter_filtering.txt
diff options
context:
space:
mode:
authorTore Darell <toredarell@gmail.com>2008-10-07 20:51:00 +0200
committerTore Darell <toredarell@gmail.com>2008-10-07 20:51:00 +0200
commitdfc0b1a716d17085224a375977a10407ba9bea24 (patch)
tree80a9ab9ad2105f758e8155bf6029fb020e028d4c /railties/doc/guides/actioncontroller/parameter_filtering.txt
parent3da0c0a8424ce018fa756e906e824698dfdcb65e (diff)
downloadrails-dfc0b1a716d17085224a375977a10407ba9bea24.tar.gz
rails-dfc0b1a716d17085224a375977a10407ba9bea24.tar.bz2
rails-dfc0b1a716d17085224a375977a10407ba9bea24.zip
Add verification, rescue + fixes to AC basics
Diffstat (limited to 'railties/doc/guides/actioncontroller/parameter_filtering.txt')
-rw-r--r--railties/doc/guides/actioncontroller/parameter_filtering.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/doc/guides/actioncontroller/parameter_filtering.txt b/railties/doc/guides/actioncontroller/parameter_filtering.txt
index dce4b252c3..663549d130 100644
--- a/railties/doc/guides/actioncontroller/parameter_filtering.txt
+++ b/railties/doc/guides/actioncontroller/parameter_filtering.txt
@@ -1,6 +1,6 @@
== Parameter filtering ==
-Rails keeps a log file for each environment (development, test and production) in the "log" folder. These are extremely useful when debugging what's actually going on in your application, but in a live application you may not want every bit of information to be stored in the log file. The "filter_parameter_logging":http://api.rubyonrails.org/classes/ActionController/Base.html#M000837 can be used to filter out sensitive information from the log. It works by replacing certain keys in the `params` hash with "[FILTERED]" before they are written to the log. As an example, let's see how to filter all parameters with keys that include "password":
+Rails keeps a log file for each environment (development, test and production) in the "log" folder. These are extremely useful when debugging what's actually going on in your application, but in a live application you may not want every bit of information to be stored in the log file. The "filter_parameter_logging":http://api.rubyonrails.org/classes/ActionController/Base.html#M000837 method can be used to filter out sensitive information from the log. It works by replacing certain keys in the `params` hash with "[FILTERED]" as they are written to the log. As an example, let's see how to filter all parameters with keys that include "password":
[source, ruby]
-------------------------