GUIDES
GDPR requires genuine opt-in consent before non-essential cookies are set — this means holding off on analytics and marketing cookies until the user actually agrees, not just displaying a banner.
How Laravel's broadcasting system turns a server-side event into a message a browser receives instantly — and what actually needs to run for it to work.
The CSRF token embedded in a page's initial HTML goes stale the moment the session it was generated for expires — a long-open browser tab is the single most common real-world trigger for this exact exception.
JWT auth trades Sanctum's simpler cookie/token model for a fully stateless token the server never stores — useful specifically for a mobile app or third-party API consumer, not typical for a first-party web app.
Header names are matched case-insensitively — $request->header('Content-Type') and $request->header('content-type') both work identically, since the HTTP spec itself never treats header casing as meaningful.
The IP address a proxy or load balancer reports needs to be trusted explicitly, or Laravel returns the proxy's own address instead of the real visitor's — the same trustProxies configuration the HTTPS-scheme detection issue depends on.
A Blade component packages markup and logic into a reusable piece with its own props — anonymous components for pure markup, class-based ones when real logic is needed behind them.
Laravel's Mail facade works the same regardless of the underlying transport — the differences are all in the .env configuration, covered here for the most common providers.
Combining search, image upload, and pagination in one CRUD app is really three previously-covered patterns composed together, not a genuinely new technique on its own.
Laravel's File and Storage facades cover checking, creating, copying, and deleting folders — for zipping, PHP's built-in ZipArchive class does the actual work.
The Hash facade, why bcrypt/argon2 hashes look different every time for the same password, and the correct way to verify a login without ever decrypting anything.
Applying a watermark before saving, not as a separate later step, is what guarantees a watermarked image can never accidentally be served without its watermark already baked in.
