Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
39 lines (30 sloc) 2.48 KB
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[Category: cool_gems | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/cool-gems/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
<updated>2012-12-19T19:57:09+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
</author>
<generator uri="http://octopress.org/">Octopress</generator>
<entry>
<title type="html"><![CDATA[Rack protection - another cool gem]]></title>
<link href="http://luisalima.github.com/blog/2012/12/13/rack-protection-another-cool-gem/"/>
<updated>2012-12-13T14:01:00+00:00</updated>
<id>http://luisalima.github.com/blog/2012/12/13/rack-protection-another-cool-gem</id>
<content type="html"><![CDATA[<p>This one I haven't evaluated yet, but looks promising: <a href="http://rkh.github.com/rack-protection/">Rack Protection</a>, to prevent typical web attacks such as <a href="https://www.owasp.org/index.php/Cross-Site_Request_Forgery">cross site request forgery</a>, <a href="https://www.owasp.org/index.php/Cross_site_scripting">cross site scripting</a>, <a href="https://www.owasp.org/index.php/Clickjacking">clickjacking</a>, directory traversal, <a href="https://www.owasp.org/index.php/Session_hijacking_attack">session hijacking</a> and IP spoofing.</p>
]]></content>
</entry>
<entry>
<title type="html"><![CDATA[Better errors gem]]></title>
<link href="http://luisalima.github.com/blog/2012/12/13/better-errors-gem/"/>
<updated>2012-12-13T11:29:00+00:00</updated>
<id>http://luisalima.github.com/blog/2012/12/13/better-errors-gem</id>
<content type="html"><![CDATA[<p>Yes, today I am in "documentation" mode, which means "bloggation" mode :-)</p>
<p>Just installed this gem -- <a href="https://github.com/charliesome/better_errors">Better errors</a>. It is a gem meant to help you out in development mode that replaces the standard Rails error page with a wayyyy better and more useful error page, featuring full stack trace, source code inspection for all stack frames, local and instance variable inspection, etc.</p>
<p>I'm going to try it out today, but definitely beats the time spent looking at development logs (even if they are as clean and contained as mine after doing the changes described in <a href="/blog/2012/12/13/disabling-nagging-logs-in-rails">this post</a>).</p>
]]></content>
</entry>
</feed>
Something went wrong with that request. Please try again.