@IntrusionCM Yeah, pretty much. I'd have assumed that http_response_code() would give me, y'know, the *actual response code* and not just 200 by default. Nginx knows what the response code is and it can evidently already pass additional information to PHP, but in this case it doesn't.

The error page redirect always worked fine, no problems there, it's just that PHP is a dumbass and is configured to assume "oh, I'm running? must be 200 OK" by default.

@IntrusionCM I regret to inform you that I am my own admin, and I have no idea what the fuck I'm doing

@donkulator I finally figured it out in the end, at least! I had to jank my way around http_response_code() entirely and set the REDIRECT_STATUS parameter in fastcgi.conf to $status

This let me get the response code from Nginx using $_SERVER["REDIRECT_STATUS"] in PHP, with the caveat that 200 (OK) returns as 000

It's so janky, but it works

@WeAreMany First I've heard about that, actually. I'll take a gander at the news.

@hjk101 Yeah! Normally I would just go ahead and install it, but I'm keeping my stack as slim as possible given the limited hardware at my disposal. It's a personal project too, so thankfully I don't really have to worry about anyone else's workflow/what they use.

Kudos to the Pi though, it's a fair bit more capable than I thought!

"finally, I can google something else! I was running out of search results for the last error..."