Create a middleware using php artisan make:middleware AddCspHeaders and implement the CSP header in the handle method with a policy like default-src 'self'; while avoiding 'unsafe-inline' and 'unsafe-eval' in production; 2. Register the middleware globally in the $middleware array or apply it to specific routes or groups in app/Http/Kernel.php; 3. Customize the policy based on required sources, such as allowing external domains for analytics or CDNs, and use nonces for inline scripts instead of unsafe directives; 4. Optionally, enable reporting by adding a report-uri directive and create a route to log violations while disabling CSRF protection for that endpoint; 5. Test the policy thoroughly, start with a strict configuration, and adjust as needed to balance security and functionality, ensuring your Laravel application is protected against XSS and injection attacks through an effective CSP implementation.
Setting up a Content Security Policy (CSP) in Laravel helps protect your application from cross-site scripting (XSS), data injection, and other client-side attacks by restricting which resources (scripts, styles, images, etc.) can be loaded. Laravel doesn’t include CSP by default, but you can implement it effectively using middleware. Here's how.

1. Create a CSP Middleware
Start by generating a middleware that will add the Content-Security-Policy
header to your HTTP responses.
Run this Artisan command:

php artisan make:middleware AddCspHeaders
Then, open the newly created file app/Http/Middleware/AddCspHeaders.php
and modify the handle
method:
<?php namespace App\Http\Middleware; use Closure; class AddCspHeaders { public function handle($request, Closure $next) { $response = $next($request); // Only apply CSP in production if (app()->environment('production')) { $csp = "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; frame-ancestors 'self'; object-src 'none'; form-action 'self';"; $response->header('Content-Security-Policy', $csp); } return $response; } }
? Note: Avoid
'unsafe-inline'
and'unsafe-eval'
in production if possible. Use nonces or hashes instead for better security.
2. Register the Middleware
You need to register the middleware so Laravel applies it to requests.
Option A: Global Middleware (applies to all routes)
Add it to the $middleware
array in app/Http/Kernel.php
:
protected $middleware = [ // other middleware \App\Http\Middleware\AddCspHeaders::class, ];
Option B: Route-specific Middleware
If you only want CSP on certain routes, assign it to a middleware group or individual route.
First, add it to a group in Kernel.php
:
protected $middlewareGroups = [ 'web' => [ // other middleware \App\Http\Middleware\AddCspHeaders::class, ], ];
Or apply it directly to a route:
Route::get('/secure', function () { return view('secure'); })->middleware(AddCspHeaders::class);
3. Customize the CSP Policy
Tailor the policy based on your app’s needs. For example:
If you use Google Analytics or CDNs:
script-src 'self' https://www.google-analytics.com 'unsafe-inline'; img-src 'self' https://www.google-analytics.com data:;
If you use inline scripts (not recommended), use nonces:
Generate a nonce per request:
$nonce = base64_encode(random_bytes(16));
Then set:
script-src 'self' 'nonce-' . $nonce;
And in your Blade templates:
<script nonce="{{ $nonce }}"> console.log("This is allowed"); </script>
Pass the nonce via
view()->share()
or middleware.
4. Use Reporting (Optional)
You can also set up CSP reporting to monitor violations:
Add report-uri
or report-to
directive:
$csp = "default-src 'self'; ...; report-uri /csp-report;";
Then create a route to handle reports:
Route::post('/csp-report', function () { \Log::warning('CSP Violation:', request()->all()); return response('', 204); })->withoutMiddleware([\App\Http\Middleware\VerifyCsrfToken::class]);
?? Disable CSRF for this endpoint since CSP reports are sent cross-origin.
Summary
- ? Create middleware to inject the CSP header
- ? Register it in
Kernel.php
or on specific routes - ? Customize directives based on your assets and domains
- ? Avoid unsafe practices when possible
- ? Use reporting to catch and fix issues
With a properly configured CSP, your Laravel app becomes significantly more resilient to XSS and injection attacks. Start strict, test thoroughly, and adjust as needed.
Basically, it’s not hard to set up — just a middleware and some careful policy tuning.
The above is the detailed content of How to set up a Content Security Policy (CSP) in Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to add custom validation rules in Laravel: using closures, Rule classes, and form requests. 1. Use closures to be suitable for lightweight verification, such as preventing the user name "admin"; 2. Create Rule classes (such as ValidUsernameRule) to make complex logic clearer and maintainable; 3. Integrate multiple rules in form requests and centrally manage verification logic. At the same time, you can set prompts through custom messages methods or incoming error message arrays to improve flexibility and maintainability.

The core methods for Laravel applications to implement multilingual support include: setting language files, dynamic language switching, translation URL routing, and managing translation keys in Blade templates. First, organize the strings of each language in the corresponding folders (such as en, es, fr) in the /resources/lang directory, and define the translation content by returning the associative array; 2. Translate the key value through the \_\_() helper function call, and use App::setLocale() to combine session or routing parameters to realize language switching; 3. For translation URLs, paths can be defined for different languages ??through prefixed routing groups, or route alias in language files dynamically mapped; 4. Keep the translation keys concise and

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

ServiceProvider is the core mechanism used in the Laravel framework for registering services and initializing logic. You can create a custom ServiceProvider through the Artisan command; 1. The register method is used to bind services, register singletons, set aliases, etc., and other services that have not yet been loaded cannot be called; 2. The boot method runs after all services are registered and is used to register event listeners, view synthesizers, middleware and other logic that depends on other services; common uses include binding interfaces and implementations, registering Facades, loading configurations, registering command-line instructions and view components; it is recommended to centralize relevant bindings to a ServiceProvider to manage, and pay attention to registration

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

The core methods for handling exceptions and recording errors in Laravel applications include: 1. Use the App\Exceptions\Handler class to centrally manage unhandled exceptions, and record or notify exception information through the report() method, such as sending Slack notifications; 2. Use Monolog to configure the log system, set the log level and output method in config/logging.php, and enable error and above level logs in production environment. At the same time, detailed exception information can be manually recorded in report() in combination with the context; 3. Customize the render() method to return a unified JSON format error response, improving the collaboration efficiency of the front and back end of the API. These steps are
