My Laravel site was working just fine yesterday but after a code-only update today I was seeing 502 errors on some pages

upstream sent too big header while reading response header from upstream, client:

• phpfpm + nginx in kubernetes
• Laravel Https Behind a Proxy

While the solution was hard to find it was easy to implement.

Yesterday I thought I’d fixed my https links on Laravel running in Kubernetes - but I had a nagging feeling that I’d just followed some random blog posts and missed something …

Unfortunately what I had looked for was force laravel to use https

When what I really needed was Configuring Trusted Proxies

As a backend developer I’m a big fan of Bootstrap it is a framework that lets me quickly put together user interfaces with consistent components using Modals, Alerts, Toasts and more - things that I don’t want to have to learn how to make work and add design to.

It seems like Laravel used to use Bootstrap by default but has migrated to Tailwind CSS

So far on my Kubernetes journey I’ve only ever had one container per pod.

But I needed to run php-fpm fronted by nginx - with static assets served direct by nginx.

A lot of online examples skip this complexity by serving both php and static assets via Apache.

While it seemed complex at first - like a lot of Kubernetes it’s fairly straightforward once you have made the leap.