Improvement of BaseUrl-Handling including Windows-Support

[glady]

When I have a server running on Windows, there are some problems with determinating the baseUrl, when no base-path is requested.

Example 1:

• document root = X:\someRootPath
• url = http://localhost/base/path/index.php
• $_SERVER['SCRIPT_NAME'] = '/base/path/index.php'
• Jentin-baseUrl = '/base/path/'
• expected baseUrl = '/base/path' (no trailing /)

Example 2:

• document root = X:\someRootPath\base\path
• url = http://localhost/index.php
• $_SERVER['SCRIPT_NAME'] = '/index.php'
• Jentin-baseUrl = '/' (Bug: dirname on Windows returns \ when path is empty; then trailing /)
• expected baseUrl = ''

[glady]

Commit https://github.com/glady/Jentin/commit/ed900cc60ded9c38a222433e4ae21533e3156c99 adds a test case to base-url UnitTest that proves, that there is a problem with routing without baseUrl ('http://localhost/module/controller/action' says baseUrl is '/module/controller/', not '/' like expected by old behavior with trailing / or '' without it)

[glady]

Tested with a local apache instance:

Request with var_dump of $_SERVER on url http://localhost:8080/module/controller/action
$_SERVER contains
'DOCUMENT_ROOT' => string 'C:/path/to/script'
'SCRIPT_FILENAME' => string 'C:/path/to/script/server.php'
'REQUEST_URI' => string '/module/controller/action'
'SCRIPT_NAME' => string '/server.php'
server.php should now apply Jentin routes defined, but it does define '/module/controller/' as basePath, which is not intended.

Conclusion: FileSystem paths CAN be completely different from uri, because uri can contain routing logic.