Fait confiance aux reverse proxies pour la détection HTTPS
Sans TrustProxies, Laravel ignore X-Forwarded-Proto derrière un proxy qui termine le TLS et génère les URLs d'assets en http://, provoquant des erreurs de contenu mixte sur les pages servies en https://. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
01233928cc
commit
2bf169ed88
@@ -12,6 +12,12 @@ return Application::configure(basePath: dirname(__DIR__))
|
||||
health: '/up',
|
||||
)
|
||||
->withMiddleware(function (Middleware $middleware): void {
|
||||
// The app runs behind a reverse proxy that terminates TLS and forwards
|
||||
// plain HTTP — without this, Laravel doesn't know the original request
|
||||
// was HTTPS and generates asset/URL links as http://, which browsers
|
||||
// then block as mixed content on an https:// page.
|
||||
$middleware->trustProxies(at: '*');
|
||||
|
||||
$middleware->alias([
|
||||
'org.ip_access' => \App\Http\Middleware\CheckOrganizationIpAccess::class,
|
||||
'role' => \Spatie\Permission\Middleware\RoleMiddleware::class,
|
||||
|
||||
Reference in New Issue
Block a user