The Wire · Showcase
Valet 413 upload bug fixed
By RepoJournal · Filed · About Laravel
Valet's hidden 413 on HTTP sites is gone, unifying upload limits at 512M.
Laravel Valet shipped a fix overnight that eliminates a confusing upload failure: sites served over plain HTTP rejected uploads between 128M and 512M with a 413, while HTTPS handled them fine [1]. The root cause: `client_max_body_size` was set to 512M only in the top-level nginx config and the secure HTTPS block, but every other server block capped at 128M [1]. The PR sets 512M consistently across all site, proxy, and share blocks, aligning with the PHP upload limits in `php-memory-limits.ini` [1]. It's already merged, so pull the latest Valet and restart to get the fix [2]. Meanwhile, Telescope is quiet, with a test-improvements PR [4] that adds no new features [3]. If you rely on local HTTPS, you likely never hit this bug, but HTTP users should update immediately.
One email a day. Unsubscribe in one click.
Keep up with Laravel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Update Valet to the latest commit so plain-HTTP sites accept uploads up to 512M laravel/valet [immediate]
- → Skip the Telescope test-only PR for now; no functional change laravel/telescope [monitor]
References
- [1] Match client_max_body_size to Valet's PHP upload limits ↗ laravel/valet
- [2] Merge pull request #1570 from webpatser/unify-body-size laravel/valet
- [3] Test improvements ↗ laravel/telescope
- [4] Test improvements (#1759) laravel/telescope