<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 06:50:13 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Henrik Bj&oslash;rnskov' Blog: Symfony2: Quick tip for your security configuration]]></title>
      <guid>http://www.phpdeveloper.org/news/17307</guid>
      <link>http://www.phpdeveloper.org/news/17307</link>
      <description><![CDATA[<p>
<i>Henrik Bj&oslash;rnskov</i> has a <a href="http://henrik.bjrnskov.dk/symfony2-security-configuration-tip/">quick new post</a> with a security tip for those using the Symfony2 framework in its configuration.
</p>
<blockquote>
Earlier when playing around with the Security component and SecurityBundle i found that for all paths you can specify a route name and the component will match it when check for the request paths. 
</blockquote>
<p>
Setting this up in your configuration gives you more control over the paths that are matched as well as more flexibility in defining them. He includes a note about a change you might have to make to the SecurityBundle's code to get the "check_path" part working correctly. You can find out more about the SecurityBundle's integration in <a href="http://tracehello.wordpress.com/2011/07/25/symfony2-securitybundle/">this blog post</a> from <i>Pablo Bandin</i>.
</p>]]></description>
      <pubDate>Tue, 27 Dec 2011 08:40:45 -0600</pubDate>
    </item>
  </channel>
</rss>
