This mirrors my experience exactly - it took me an embarrassingly long time to learn about http and what it means to be stateless.
It also took learning other languages to understand how PHP is so unique in how tied to HTTP it is (rebuilding its entire universe every request).
(these learnings happened when moving beyond the PHP-based CMS style of development - agency style work on my case - to make more custom software).
I imagine it took you awhile to understand what “stateless“ meant, because you weren’t exposed to the default state-fullness of most other languages, so didn’t realize stateless wasn’t the default.
When I did learn about HTTP, it was very easy, since I already knew it without knowing I knew it, so maybe that's in favor of your point, but there's much to be said for the actual understanding that I didn't have at first. When I started interviewing people for PHP entry-level jobs, asking about HTTP was one of the ways I gauged how well applicants understood their work at a conceptual level.