Detect the tracked page URL from REQUEST_URI instead of PATH_INFO

[sgiehl]

Supersedes #141.

Problem

getCurrentScriptName() builds the auto-detected page URL (the path between the host and the query string, consumed by getCurrentUrl()). It preferred $_SERVER[PATH_INFO], which only holds the trailing path-info segment — always just a suffix of the requested path.

With front-controller / path-info routing this truncates the URL. For a request to https://example.com/dir1/page, where dir1/index.php handles /page via a rewrite:

Variable	Value
REQUEST_URI	/dir1/page
PATH_INFO	/page
SCRIPT_NAME	/dir1/index.php

The tracker recorded /page instead of /dir1/page, silently dropping the directory prefix.

Fix

Use REQUEST_URI as the source (it already contains the full requested path, including any path-info) and drop PATH_INFO entirely. SCRIPT_NAME remains the fallback when REQUEST_URI is unavailable. This also aligns the primary source with Matomo core’s Url::getCurrentScriptName().

The original report and patch swapped the priority order but kept PATH_INFO as a fallback; since PATH_INFO can only ever yield a truncated path for this method’s purpose, it is removed rather than merely deprioritized.

Notes

• Behavior change only affects sites using path-info routing, and moves them from a broken to a correct URL.
• Updated the existing unit tests (which asserted the old PATH_INFO-first behavior) and added a regression test for the reporter’s scenario.
• CHANGELOG updated under 4.0.0.

Reported by @schorschii in #141.