PHP Implementation for Retrieving Full URL Path Information on Windows/IIS Servers

Problem Context and Challenges

In web development practice, particularly in scenarios involving website migration and URL redirection, accurately obtaining complete URL path information for current pages represents a critical technical requirement. The user-reported case involves WordPress installation migration from original locations to new folders on Windows/IIS servers, where configured 301 redirect functionality fails to operate correctly. The specific manifestation involves expected URL format http://www.example.com/OLD_FOLDER/index.php/post-title/, with inability to reliably extract the /post-title/ path segment.

Environmental Differences Between IIS and Apache

In standard Apache server environments, developers typically rely on the $_SERVER["REQUEST_URI"] global variable to obtain complete request URI information. However, in Windows/IIS server environments, this variable may return empty strings, failing to meet development requirements. Similarly, the $_SERVER["PHP_SELF"] variable returns only index.php, unable to provide comprehensive path information.

This discrepancy originates from different URL request processing mechanisms between IIS and Apache. As Microsoft's web server, IIS exhibits significant differences in URL parsing logic compared to open-source Apache servers, particularly in handling path information and script mapping.

Core Solution Using PATH_INFO Variable

Addressing URL path acquisition requirements in IIS environments, the $_SERVER["PATH_INFO"] variable provides an effective solution. This variable specifically retrieves client-provided path information segments, accurately returning path fragments like /post-title/ in the described URL format.

Basic implementation code based on PATH_INFO variable:

<?php
// Retrieve path information
$path_info = isset($_SERVER['PATH_INFO']) ? $_SERVER['PATH_INFO'] : '';

// Application in WordPress redirection scenarios
if (!empty($path_info)) {
    // Extract post title segment
    $post_title = trim($path_info, '/');
    
    // Execute 301 redirection logic
    header("HTTP/1.1 301 Moved Permanently");
    header("Location: http://www.example.com/NEW_FOLDER/" . $post_title);
    exit;
}
?>

In-depth Analysis of IIS Server Variables

According to official IIS server variable documentation, PATH_INFO variable specifically stores client-provided path information. For example, with URL /vdir/myisapi.dll/zip, PATH_INFO returns the /zip segment. This characteristic makes it particularly suitable for handling friendly URL structures in CMS systems like WordPress.

Note that IIS's AllowPathInfoForScriptMappings metabase property setting affects PATH_INFO behavior. When this property is set to true (primarily for supporting pure CGI functionality), PATH_INFO contains only the path information segment, which may impact normal operation of certain ISAPI applications.

Supplementary Complete URL Construction Methods

Beyond path information retrieval, complete URL address construction is typically required in practical development. Complete URL construction method combining multiple server variables:

<?php
function getFullURL() {
    $protocol = (!empty($_SERVER['HTTPS']) && $_SERVER['HTTPS'] !== 'off') ? "https://" : "http://";
    $host = $_SERVER['HTTP_HOST'] ?? $_SERVER['SERVER_NAME'];
    $port = ($_SERVER['SERVER_PORT'] != '80' && $_SERVER['SERVER_PORT'] != '443') ? ":" . $_SERVER['SERVER_PORT'] : '';
    $path = $_SERVER['REQUEST_URI'] ?? '';
    
    return $protocol . $host . $port . $path;
}

// In IIS environments, can combine with PATH_INFO
function getFullURLWithPathInfo() {
    $base_url = getFullURL();
    $path_info = $_SERVER['PATH_INFO'] ?? '';
    
    return $base_url . $path_info;
}
?>

Security Considerations and Best Practices

When utilizing server variables, security concerns must be addressed. IIS official documentation explicitly states that certain server variable information originates from HTTP headers, which malicious users might forge. Particularly in scenarios involving user authentication and authorization, rigorous validation and filtering of acquired data is essential.

Recommended security practices include:

• Implement input validation for all data obtained from server variables
• Note differences in domain name resolution when using HTTP_HOST and SERVER_NAME
• Validate target URL legitimacy in redirection operations
• Employ standardized error handling mechanisms

Server Configuration Optimization Recommendations

To ensure PATH_INFO variable functions correctly in IIS environments, the following server configuration is recommended:

• Verify correct IIS script mapping configuration
• Check AllowPathInfoForScriptMappings property setting
• Ensure proper PHP handler configuration
• Configure appropriate rewrite rules in web.config

Cross-Server Compatibility Considerations

For applications requiring operation across both IIS and Apache environments, compatibility handling is recommended:

<?php
function getRequestPath() {
    // Prioritize PATH_INFO (IIS environment)
    if (isset($_SERVER['PATH_INFO']) && !empty($_SERVER['PATH_INFO'])) {
        return $_SERVER['PATH_INFO'];
    }
    
    // Fallback: Parse REQUEST_URI (Apache environment)
    if (isset($_SERVER['REQUEST_URI'])) {
        $request_uri = $_SERVER['REQUEST_URI'];
        // Remove query string and script path
        if (($pos = strpos($request_uri, '?')) !== false) {
            $request_uri = substr($request_uri, 0, $pos);
        }
        $script_name = $_SERVER['SCRIPT_NAME'] ?? '';
        if (strpos($request_uri, $script_name) === 0) {
            $request_uri = substr($request_uri, strlen($script_name));
        }
        return $request_uri;
    }
    
    return '';
}
?>

Practical Application Scenario Extensions

PATH_INFO-based URL handling solutions apply not only to WordPress migration scenarios but also extensively to:

• Custom routing system implementation
• RESTful API path parameter parsing
• Multilingual website content routing
• Dynamic content loading URL processing

Through rational utilization of IIS server variables, developers can construct more robust and flexible web applications, effectively addressing URL processing challenges in Windows server environments.