118 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-08-27
stories 5

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Valet 413 upload bug fixed

By RepoJournal · Filed · About Laravel · Composed from the cited sources · methodology

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.

Quick answers

What shipped in Laravel on August 27, 2026?
Valet's hidden 413 on HTTP sites is gone, unifying upload limits at 512M. In total, 3 commits and 2 pull requests landed.
Who contributed to Laravel on August 27, 2026?
3 developers shipped this update, including crynobone, webpatser, and Matt Stauffer.
What were the notable Laravel updates?
Match client_max_body_size to Valet's PHP upload limits, Merge pull request #1570 from webpatser/unify-body-size, and Test improvements.