Laravel's Signed URLs are signed URLs that generate links with timeliness and verification mechanisms to ensure that the links are not tampered with. It generates a signature based on routing parameters and APP_KEY. If the parameters are modified, the signature will be invalid. Use URL::signedRoute() to create permanent valid links; use URL::temporarySignedRoute() to create limited-time links; in the controller, you can verify signatures through the validSignature() method or the middleware ValidateSignature; common application scenarios include email verification, one-time download link, invitation link and API interface access control; precautions include signature dependency APP_KEY, avoiding exposure of sensitive parameters, and multi-parameters need to participate in signature calculation. The default algorithm is SHA-256.
Laravel's Signed URLs are signed URLs that allow you to generate a time-sensitive, verified link that ensures that the link is accessed without tampering. This mechanism is often used in scenarios where temporary authorization access is required, such as: email confirmation, one-time download link, public access to restricted resources, etc.

What are Laravel's Signed URLs?
Simply put, Signed URL is a normal URL with signature parameters attached. This signature is generated based on routing parameters and application key (APP_KEY) to verify whether the request source is legal. If someone manually modify the parameters in the URL, the signature will no longer match and Laravel will reject the request.
By default, signature information is placed in signature
query parameters, for example:

https://example.com/verify-email?signature=abc123xyz
How to create a Signed URL?
Laravel provides a very concise way to generate signed URLs. Usually, URL::signedRoute()
or temporarySignedRoute()
methods are used.
Create a permanent valid signature using signedRoute()
use Illuminate\Support\Facades\URL; $url = URL::signedRoute('verify.email', ['user' => 1]);
This link will be valid once it is generated unless you manually change the key or clear the cache.

Create a limited-time signature using temporarySignedRoute()
More commonly, it is to generate a time-limited link, such as only valid within 24 hours:
use Illuminate\Support\Facades\URL; use Illuminate\Support\Carbon; $url = URL::temporarySignedRoute( 'verify.email', now()->addHours(24), ['user' => 1] );
In this way, even if others get the link, they can only access it within the specified time.
How to verify Signed URL?
In the controller, you can check the validity of the signature through middleware or manually.
Method 1: Use validSignature()
method
if (! request()->hasValidSignature()) { abort(401, 'Invalid signature'); }
This code automatically checks whether the current request has a valid signature.
Method 2: Use middleware ValidateSignature
You can also add middleware to the route directly:
Route::get('/verify-email', [VerifyController::class, 'index'])->name('verify.email')->middleware('signed');
If the signature is invalid or expired, the middleware will automatically return a 403 error.
Examples of practical application scenarios
- Email Verification : After registering, the user sends a signed verification email.
- One-time download link : Provide users with a secure and limited-time file download address.
- Invite links : For example, when inviting someone to join a team, generate a unique link with a signature.
- API Interface Open Access : Some API routing that does not require login but wants to prevent abuse.
For example, suppose you want the user to click on a link in the email to activate the account, you can use the Signed URL to ensure that only the person who received the email can perform this operation.
Notes and tips
- Signature depends on
APP_KEY
, so if you replaceAPP_KEY
in the.env
file, the old signature will be invalid. - Do not expose sensitive data to URL parameters, even signed links.
- If you need multiple parameters, make sure they are all included in the signature calculation.
- You can check whether the timeout is achieved through
request()->signatureHasNotExpired()
. - The default signature algorithm is SHA-256.
Basically all that is it. If you master these methods, you can use Signed URLs flexibly in your project.
The above is the detailed content of Explain Laravel Signed URLs.. 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)

There are three main ways to set environment variables in PHP: 1. Global configuration through php.ini; 2. Passed through a web server (such as SetEnv of Apache or fastcgi_param of Nginx); 3. Use putenv() function in PHP scripts. Among them, php.ini is suitable for global and infrequently changing configurations, web server configuration is suitable for scenarios that need to be isolated, and putenv() is suitable for temporary variables. Persistence policies include configuration files (such as php.ini or web server configuration), .env files are loaded with dotenv library, and dynamic injection of variables in CI/CD processes. Security management sensitive information should be avoided hard-coded, and it is recommended to use.en

Laravel's configuration cache improves performance by merging all configuration files into a single cache file. Enabling configuration cache in a production environment can reduce I/O operations and file parsing on each request, thereby speeding up configuration loading; 1. It should be enabled when the application is deployed, the configuration is stable and no frequent changes are required; 2. After enabling, modify the configuration, you need to re-run phpartisanconfig:cache to take effect; 3. Avoid using dynamic logic or closures that depend on runtime conditions in the configuration file; 4. When troubleshooting problems, you should first clear the cache, check the .env variables and re-cache.

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

Laravel's EloquentScopes is a tool that encapsulates common query logic, divided into local scope and global scope. 1. The local scope is defined with a method starting with scope and needs to be called explicitly, such as Post::published(); 2. The global scope is automatically applied to all queries, often used for soft deletion or multi-tenant systems, and the Scope interface needs to be implemented and registered in the model; 3. The scope can be equipped with parameters, such as filtering articles by year or month, and corresponding parameters are passed in when calling; 4. Pay attention to naming specifications, chain calls, temporary disabling and combination expansion when using to improve code clarity and reusability.

User permission management is the core mechanism for realizing product monetization in PHP development. It separates users, roles and permissions through a role-based access control (RBAC) model to achieve flexible permission allocation and management. The specific steps include: 1. Design three tables of users, roles, and permissions and two intermediate tables of user_roles and role_permissions; 2. Implement permission checking methods in the code such as $user->can('edit_post'); 3. Use cache to improve performance; 4. Use permission control to realize product function layering and differentiated services, thereby supporting membership system and pricing strategies; 5. Avoid the permission granularity is too coarse or too fine, and use "investment"

The core idea of PHP combining AI for video content analysis is to let PHP serve as the backend "glue", first upload video to cloud storage, and then call AI services (such as Google CloudVideoAI, etc.) for asynchronous analysis; 2. PHP parses the JSON results, extract people, objects, scenes, voice and other information to generate intelligent tags and store them in the database; 3. The advantage is to use PHP's mature web ecosystem to quickly integrate AI capabilities, which is suitable for projects with existing PHP systems to efficiently implement; 4. Common challenges include large file processing (directly transmitted to cloud storage with pre-signed URLs), asynchronous tasks (introducing message queues), cost control (on-demand analysis, budget monitoring) and result optimization (label standardization); 5. Smart tags significantly improve visual

To build a PHP content payment platform, it is necessary to build a user management, content management, payment and permission control system. First, establish a user authentication system and use JWT to achieve lightweight authentication; second, design the backend management interface and database fields to manage paid content; third, integrate Alipay or WeChat payment and ensure process security; fourth, control user access rights through session or cookies. Choosing the Laravel framework can improve development efficiency, use watermarks and user management to prevent content theft, optimize performance requires coordinated improvement of code, database, cache and server configuration, and clear policies must be formulated and malicious behaviors must be prevented.
