Some webhosters offer ssl-proxies, where your site gets redirected to that proxy.
This way one can get a cheap encryption.
E.g.
http://your.domain/phpgedview
sounds with the use of a ssl-proxy like that:
https://ssl-proxy.com/your.domain/phpgedview
If you would like to use such a ssl-proxy and set in config.php values like the following, you cannot login anymore:
$SERVER_URL="https://ssl-proxy.com/your.domain/phpgedview"
and / or
$LOGIN_URL=""https://ssl-proxy.com/your.domain/phpgedview/login.php"
I assume the reason for the broken login lies in session.php, where $pgv_path and the session cookie gets set with just the dirname on "your.domain".
In this example $pgv_path is set to "/phpgedview", but it should be set to "/your.domain/phpgedview".
If you workaround and hardcode $pgv_path="/your.domain/phpgedview", then the (whole) pgv-site runs fine and encrypted through a ssl-proxy. (Just some (not all) "Close window after edit & reload site"-functions still try to load "https://ssl-proxy.com/phpgedview" ...)
With kind regards
Hansjörg
