发布于 2015-08-27 16:51:16 | 140 次阅读 | 评论: 0 | 来源: 网络整理
By default, the profiler is only activated in the development environment. But it’s imaginable that a developer may want to see the profiler even in production. Another situation may be that you want to show the profiler only when an admin has logged in. You can enable the profiler in these situations by using matchers.
Symfony provides a
built-in matcher
which can match paths and IPs. For example, if you want to only show the
profiler when accessing the page with the 168.0.0.1 IP, then you can
use this configuration:
# app/config/config.yml
framework:
# ...
profiler:
matcher:
ip: 168.0.0.1
<!-- app/config/config.xml -->
<framework:config>
<framework:profiler
ip="168.0.0.1"
/>
</framework:config>
// app/config/config.php
$container->loadFromExtension('framework', array(
'profiler' => array(
'ip' => '168.0.0.1',
),
));
You can also set a path option to define the path on which the profiler
should be enabled. For instance, setting it to ^/admin/ will enable the
profiler only for the /admin/ URLs.
You can also create a custom matcher. This is a service that checks whether
the profiler should be enabled or not. To create that service, create a class
which implements
RequestMatcherInterface. This
interface requires one method:
matches().
This method returns false to disable the profiler and true to enable the
profiler.
To enable the profiler when a ROLE_SUPER_ADMIN is logged in, you can use
something like:
// src/AppBundle/Profiler/SuperAdminMatcher.php
namespace AppBundleProfiler;
use SymfonyComponentSecurityCoreAuthorizationAuthorizationCheckerInterface;
use SymfonyComponentHttpFoundationRequest;
use SymfonyComponentHttpFoundationRequestMatcherInterface;
class SuperAdminMatcher implements RequestMatcherInterface
{
protected $authorizationChecker;
public function __construct(AuthorizationCheckerInterface $authorizationChecker)
{
$this->authorizationChecker = $authorizationChecker;
}
public function matches(Request $request)
{
return $this->authorizationChecker->isGranted('ROLE_SUPER_ADMIN');
}
}
2.6 新版功能: The AuthorizationCheckerInterface was
introduced in Symfony 2.6. Prior, you had to use the isGranted method of
SecurityContextInterface.
Then, you need to configure the service:
# app/config/services.yml
services:
app.profiler.matcher.super_admin:
class: AppBundleProfilerSuperAdminMatcher
arguments: ["@security.authorization_checker"]
<!-- app/config/services.xml -->
<services>
<service id="app.profiler.matcher.super_admin"
class="AppBundleProfilerSuperAdminMatcher">
<argument type="service" id="security.authorization_checker" />
</services>
// app/config/services.php
use SymfonyComponentDependencyInjectionDefinition;
use SymfonyComponentDependencyInjectionReference;
$container->setDefinition('app.profiler.matcher.super_admin', new Definition(
'AppBundleProfilerSuperAdminMatcher',
array(new Reference('security.authorization_checker'))
);
2.6 新版功能: The security.authorization_checker service was introduced in Symfony 2.6. Prior
to Symfony 2.6, you had to use the isGranted() method of the security.context service.
Now the service is registered, the only thing left to do is configure the profiler to use this service as the matcher:
# app/config/config.yml
framework:
# ...
profiler:
matcher:
service: app.profiler.matcher.super_admin
<!-- app/config/config.xml -->
<framework:config>
<!-- ... -->
<framework:profiler
service="app.profiler.matcher.super_admin"
/>
</framework:config>
// app/config/config.php
$container->loadFromExtension('framework', array(
// ...
'profiler' => array(
'service' => 'app.profiler.matcher.super_admin',
),
));