Most of the applications we create these days usually have an admin interface where an user with necessary privileges is able to manage the application content, respecting some business rules. Thus it is required that part of this content is easily manageable, which means the user needs to be able to add some formatting to the content. For us, it usually means that the user has to input HTML tags. And it also means that the user can do things that might break our application.<\/p>\n
Luckily, Rails can help us since it has some helpers to sanitize and strip unwanted tags or attributes from the markup.<\/p>\n
If you just want to remove all links from the text you want to show, you can use the following method:<\/p>\n
<%= strip_links 'Send e-mail to <a href=\"mailto:me@example.com\">Me<\/a>.' %>\n\nSend e-mail to Me.\n<\/code><\/pre>\nStrip tags<\/h3>\n
This might be a bit famous: it removes all html tags from the given markup, using html-tokenizer:<\/p>\n
<%= strip_tags '<p class=\"foo\">Send e-mail to <a href=\"mailto:me@example.com\">Me<\/a>.<\/p>' %>\n\nSend e-mail to Me.\n<\/code><\/pre>\nSanitize<\/h3>\n
The sanitize helper encodes all html tags and strips all attributes that are not allowed, specially script tags.<\/p>\n
<%= sanitize '<p id=\"bar\" class=\"foo\">foo bar <script>alert(\"I am a hacker!\")<\/script> baz<\/p>' %>\n\n<p class=\"foo\">foo bar baz<\/p>\n<\/code><\/pre>\nFor instance here the script tag was removed, and also de id attribute from the paragraph tag.<\/p>\n
Simple format<\/h3>\n
Together with sanitize we have the simple_format helper. Besides sanitizing the given content, it automatically converts one new line into a br tag, and two or more new lines into a p tag. Lets see how it works:<\/p>\n
<%= simple_format \"I am a text \\n and I want to be formatted \\n\\n by <strong>simple_format<\/strong>\", :class => 'foo' %>\n\n<p class=\"foo\">I am a text \n<br \/> and I want to be formatted <\/p> \n<p class=\"foo\"> by <strong>simple_format<\/strong><\/p>\n<\/code><\/pre>\nSo I want to change this stuff, and now, what happens?<\/h3>\n
Rails gives you the ability to configure most of what is allowed and what is not when sanitizing content. Lets see the available options:<\/p>\n
\n- sanitized_uri_attributes<\/li>\n
- sanitized_bad_tags<\/li>\n
- sanitized_allowed_tags<\/li>\n
- sanitized_allowed_attributes<\/li>\n
- sanitized_allowed_css_properties<\/li>\n
- sanitized_allowed_css_keywords<\/li>\n
- sanitized_shorthand_css_properties<\/li>\n
- sanitized_allowed_protocols<\/li>\n<\/ul>\n
I believe these configs are pretty straightforward, but in case you have any doubt, check the docs in the source code. You can change any of these configs in your application file:<\/p>\n
class Application < Rails::Application\n config.action_view.sanitized_allowed_tags = %w(table tr th td thead tbody tfoot)\n config.action_view.sanitized_allowed_protocols = %w(tel)\nend\n<\/code><\/pre>\nWrapping up!<\/h3>\n
These simple helpers can make our life really easier when dealing with content coming from an admin interface, allowing specific tags and attributes to be shown, and doing the most they can to remove unwanted tags.<\/p>\n
You can see more about them in the docs:
\nhttp:\/\/api.rubyonrails.org\/classes\/ActionView\/Helpers\/SanitizeHelper.html
\nhttp:\/\/api.rubyonrails.org\/classes\/ActionView\/Helpers\/TextHelper.html<\/p>\n
What about you, do you use some Rails helper that might be in the dark? We would love to bring it to the light side, share with us!<\/p>\n","protected":false},"excerpt":{"rendered":"
Most of the applications we create these days usually have an admin interface where an user with necessary privileges is able to manage the application content, respecting some business rules. Thus it is required that part of this content is easily manageable, which means the user needs to be able to add some formatting to … \u00bb<\/a><\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[1],"tags":[90,7,119],"aioseo_notices":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts\/1450"}],"collection":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/comments?post=1450"}],"version-history":[{"count":18,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts\/1450\/revisions"}],"predecessor-version":[{"id":6621,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts\/1450\/revisions\/6621"}],"wp:attachment":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/media?parent=1450"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/categories?post=1450"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/tags?post=1450"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}