PHP getting full server name including port number and protocol

PHP getting full server name including port number and protocol

  1. Blog
  2. 15 November 2026
  3. 4 min read

Stefan Bogdanescu

Founder & Senior Architect

Reliable Server Name, Protocol, and Port Resolution in PHP

Determining the full origin of a request—specifically the protocol, host, and port—is a common requirement when generating URLs for redirects, API calls, or asset loading. While $_SERVER['SERVER_NAME'] reliably returns the hostname, reconstructing the other components often trips up developers working with non-standard ports or complex proxy setups.

The Protocol: Beyond Simple String Matching

The source material suggests checking the first five characters of $_SERVER['HTTP_HOST'] or $_SERVER['SERVER_PROTOCOL'] to determine if a request is HTTPS. This approach is fragile. Relying on string manipulation of $_SERVER['SERVER_PROTOCOL'] assumes the web server or reverse proxy always sends the exact header value "HTTP/1.1" or "HTTP/2". If you are behind a load balancer that terminates SSL, this header might be missing or incorrect in your PHP environment.

The robust standard is to inspect $_SERVER['HTTPS']. In most configurations, if this variable is set to "1" (case-insensitive), the connection is secure. However, there is a critical nuance: if you are behind a reverse proxy like Nginx or Apache that terminates SSL before forwarding the request to PHP, $_SERVER['HTTPS'] might default to "off" even though the user accessed the site via HTTPS. In these scenarios, relying solely on this variable requires trusting your application server configuration to pass the correct flag.

Accessing the Port Number

Getting the port number is where many implementations fail. When a browser requests https://example.com, the default port 443 is usually omitted from the URL bar. Similarly, if your PHP application sits on port 80, you rarely see that in the address bar either. However, when using custom ports like 8080 or 8888, relying on $_SERVER['HTTP_HOST'] alone is insufficient because it often strips the port unless explicitly configured by the web server to include it.

The most reliable way to retrieve the listening port in PHP is via $_SERVER['SERVER_PORT']. This variable contains the actual TCP port number the server process is bound to. If your application runs on 8080, this will return "8080". If it runs on the standard HTTP port (80), it returns "80".

Constructing the Full Origin String

To build a reliable full server name including protocol and port, you must normalize these values. Here is a pattern that handles both default ports and custom ports gracefully:

$protocol = isset($_SERVER['HTTPS']) && strtolower($_SERVER['HTTPS']) === 'on' ? 'https' : 'http';
$serverName = $_SERVER['SERVER_NAME'];
$port = $_SERVER['SERVER_PORT'];

// Remove the standard port if it matches the default for that protocol
if (($protocol === 'http' && $port == 80) || ($protocol === 'https' && $port == 443)) {
    // If you want to omit the port, do nothing here.
    // To include it, simply use $serverName . ':' . $port;
} else {
    $fullOrigin = $protocol . '://' . $serverName . ':' . $port;
}

If your application is behind a proxy and $_SERVER['HTTP_X_FORWARDED_PROTO'] or similar headers are present, you may need to trust those values instead of the raw server variables. This is a common pattern for SaaS platforms where PHP runs in a container that sees all traffic as HTTP from the proxy. In such environments, checking $_SERVER['HTTP_X_FORWARDED_PROTO'] provides a more accurate picture of the original user intent than inspecting the local socket connection.

Handling Custom Ports and Trailing Slashes

When constructing URLs programmatically, be mindful of how PHP handles trailing slashes. If you are building a redirect or a resource link, ensure that the base URL does not unexpectedly include a slash if your routing logic expects one. For instance, $_SERVER['REQUEST_URI'] often includes the query string and path but might lack a leading slash depending on your server setup.

If you are using a framework like Laravel, these details are abstracted away, but understanding the underlying variables is essential when writing custom middleware or building standalone scripts. If you need to access this information in a Laravel application specifically, request()->protocol(), request()->host(), and request()->port() provide cleaner abstractions that handle proxy headers automatically if configured correctly.

Summary of Best Practices

  1. Prefer $_SERVER['SERVER_PORT'] over parsing the host string for port numbers.
  2. Check $_SERVER['HTTPS'] carefully, keeping in mind potential issues with reverse proxies.
  3. Normalize default ports; deciding whether to display ":80" or ":443" depends on your specific URL formatting requirements.
  4. Trust proxy headers (X-Forwarded-*) when running behind a load balancer to ensure the user sees the correct origin regardless of the internal port used by PHP-FPM or Nginx.

By combining these variables logically, you can construct a consistent full server name that works whether your application is running on localhost:8080 or a production cluster on 443.

Our network