When PHP is installed as an Apache module (using Apache and PHP port installers from FreeBSD), and a script contains syntax errors or encounters problems while in use (e.g. unable to open a file with fopen), errors are reported to the browser window which reveal the absolute file path to the script rather than the relative path known by Apache, e.g. /private/database/area/php/script.php instead of /php/script.php, assuming the Apache root document directory is /private/database/area/. In several other instances, similar problems with web products (IIS, et. al.) revealing the absolute paths to their virtual environments have been labeled "bugs" or "security leaks". Please consider whether the absolute path can/should be masked whenever discretion can be obtained. I apologize if this is a configurable behavior and I just can't find the toggle, but perhaps discretion should be the default behavior if such a toggle exists. Thank you for your consideration.