diff options
| author | Nick Novitski <nicknovitski@gmail.com> | 2012-05-09 13:20:19 -0700 |
|---|---|---|
| committer | Nick Novitski <nicknovitski@gmail.com> | 2012-05-09 13:20:19 -0700 |
| commit | 3a6ffbbe42688f40edc8e0a12d0f556ef3720b9d (patch) | |
| tree | f7452cfc76594b5682cb5336a5116ca27e3ed68b /guides/source/security.textile | |
| parent | 7918d7bf5c6f0ce53e648c793f6034d6216a4808 (diff) | |
| download | rails-3a6ffbbe42688f40edc8e0a12d0f556ef3720b9d.tar.gz rails-3a6ffbbe42688f40edc8e0a12d0f556ef3720b9d.tar.bz2 rails-3a6ffbbe42688f40edc8e0a12d0f556ef3720b9d.zip | |
remove inappropriate comma
A qualifying clause beginning with words like "as", "if", or "although" should have a comma separating it from any following clauses in a sentence, but should not have a comma immediately after the beginning word, unless it is to separate a third, non-essential clause.
Example 1: "Although I would quite like to go to lunch with you, I find myself instead writing a detailed commit message to justify a single-character documentation change."
Example 2: "Despite, as you might well imagine, wishing I hadn't even noticed it in the first place, I still felt the error was worth correcting."
Diffstat (limited to 'guides/source/security.textile')
| -rw-r--r-- | guides/source/security.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/security.textile b/guides/source/security.textile index ac64b82bf6..ac55d60368 100644 --- a/guides/source/security.textile +++ b/guides/source/security.textile @@ -627,7 +627,7 @@ h4. Whitelists versus Blacklists -- _When sanitizing, protecting or verifying something, whitelists over blacklists._ -A blacklist can be a list of bad e-mail addresses, non-public actions or bad HTML tags. This is opposed to a whitelist which lists the good e-mail addresses, public actions, good HTML tags and so on. Although, sometimes it is not possible to create a whitelist (in a SPAM filter, for example), _(highlight)prefer to use whitelist approaches_: +A blacklist can be a list of bad e-mail addresses, non-public actions or bad HTML tags. This is opposed to a whitelist which lists the good e-mail addresses, public actions, good HTML tags and so on. Although sometimes it is not possible to create a whitelist (in a SPAM filter, for example), _(highlight)prefer to use whitelist approaches_: * Use before_filter :only => [...] instead of :except => [...]. This way you don't forget to turn it off for newly added actions. * Use attr_accessible instead of attr_protected. See the mass-assignment section for details |