Why is SERVER_PORT always 80 in worker mode?

[jamiecarl]

I'm hoping this is a quick question to answer. I've got an APP that automatically builds URLs based on the environment. It works fine in non-worker mode and will use port 8000, which is my listen port, to correctly construct URLs.

When I enable worker mode though, the $_SERVER['SERVER_PORT'] is always 80 and is messing up my URL generator.

Any reason for this? Is there a fix or work-around?

I can hard-code the base URL the generator uses as a work-around, but that kinda defeats it's purpose.

Cheers.

[henderkes]

I cannot reproduce your issue. SERVER_PORT is 443 for me in worker mode when I connect via https.

[henderkes]

It's showing 8000 just fine for me. You'll have to share your configuration, as this is most definitely an incorrect configuration issue.

[jamiecarl]

It's showing 8000 just fine for me. You'll have to share your configuration, as this is most definitely an incorrect configuration issue.

Ok, I have more information about what is going on and I don't think it's configuration.

Yes, if I check $_SERVER['SERVER_PORT'] during a request, it is indeed correctly returning port 8000.

However, my framework gets a bunch of stuff that shouldn't change, out of the way during bootstrap, and one of those things is resolving the server URL. So, I debugged the bootstrap process and found that $_SERVER['SERVER_PORT'] is 80 at that point.

So this is my framework index.php entrypoint:

<?php

declare(strict_types=1);

use Hazaar\Application;

if ((!($_SERVER['FRANKENPHP_WORKER'] ?? false)) || !function_exists('frankenphp_handle_request')) {
    echo 'FrankenPHP must be in worker mode to use this script.';

    exit(1);
}

// Prevent worker script termination when a client connection is interrupted
ignore_user_abort(true);

// Composer autoloading
include __DIR__.'/../vendor/autoload.php';

// Create a new application
$app = new Application($_ENV['APPLICATION_ENV'] ?? 'development');
$app->bootstrap();

// Handler outside the loop for better performance (doing less work)
$handler = static function () use ($app) {
    $app->timer->reset();
    $app->run();
};

$requestCount = 0;
$maxRequests = (int) ($_ENV['MAX_REQUESTS'] ?? $_SERVER['MAX_REQUESTS'] ?? 1000);

while ($requestCount < $maxRequests && frankenphp_handle_request($handler)) {
    ++$requestCount;
    gc_collect_cycles();
}

// Cleanup
$app->shutdown();

So where it calls $app->bootstrap() is where it looks at $_SERVER['SERVER_PORT'] and at that point, the port is 80. Once it enters the main loop and executes the handler function with frankenphp_handle_request($handler), that's when the port changes to 8000.

So, is this a bug, or by design?

Knowing that this is how it works now, I can implement a work-around by just not pre-initialising the URL generator. So thanks for leading me to a solution.

But if this isn't how it's supposed to work..... well.....

Thanks.

[jamiecarl]

Here is a screenshot of $_SERVER from the debug console during application startup.

But once it starts handling requests, the port changes to 8000.

[henderkes]

Of course, we can't know the server port of a worker before a request comes in. So you could say it's "by design".

E.g.

:8000, :8001 {
    php_server {
        worker /index.php
     }
}

What is the SERVER_PORT here? Even:

localhost {
     php_server {
          worker index.php
     }
}

Is it :80? Is it 443? What is the PROTO? TCP? UDP?

If you "know" ahead of time, you can pass this information to the worker:

:8000 {
    php_server {
        worker {
            file index.php
            env SERVER_PORT 8000
         }
     }
}

[jamiecarl]

Of course, it makes sense now. I haven't used worker mode, or FrankenPHP at all in fact, with multiple listen ports for different services, so it makes sense now that the port will change to wherever the request is coming in on. Good to know.

I've updated my framework so that any use of $_SERVER is no longer used during bootstrap. This was affecting mainly the URL generator, which in turn affected JWT token issuers and caused false negative auth responses. Everything is humming along nicely now with worker mode both on and off.

Thanks for the insight.