PHP documents the presence ofHTTPS within$_SERVER (seehttps://www.php.net/manual/en/reserved.variables.server.php), not$_ENV.
And I believe most of the literature online also references$_SERVER.

So I think we are within spec here, your app should probably be fixed instead.

Also I don't quite understand how your application could even be reached if the router exited before the call toarray_merge 🤔

After thatreturn false; it just continues to myindex.php, not really sure how that works, maybe the router file is set as anauto_prepend_file 🤔

PHP documents the presence ofHTTPS within$_SERVER (seehttps://www.php.net/manual/en/reserved.variables.server.php), not$_ENV.
And I believe most of the literature online also references$_SERVER.

The problem is that the code in the$envFile only sets$_ENV['https'] = 'on', but nothing on the$_SERVER and that is why the merge is needed in the first place

Oh ok sorry I got that the wrong way.

So I believe the change might makes sense, but at the same time this is the location this merge has been present for quite a long time in Symfony so I'm not entirely sure of the consequences this could have...

Another approach would be to change how we generate the env for the PHP CLI server to make sure the right keys are populated for_SERVER, something along those lines:https://github.com/symfony-cli/symfony-cli/compare/main...tucksaun:symfonycli:fix-generate-server-superglobal-cli-server?expand=1

wdyt@fabpot ?

@tucksaun I actually like your version, no point in setting the variables on$_ENV which are supposed to be in$_SERVER anyways 👍