Issue #816 has been updated by Sébastien COLLIN.
This kind of problem also happen if you use NginX and the server name is "_" (underscore), which is the catch all character for server name. I think it's a good idea to give the possibility to specify protocol / server name in the configuration file in order to avoid this kind of problem (which can also happen with any proxy system, quite common nowadays because of technologies like Docker). I would just add a "flag" guess URL instead of checking if $request_url is set. ---------------------------------------- Bug #816: PHP receives incorrect SERVER_NAME when used behind SSL accelerator http://tools.lsc-project.org/issues/816 Author: Karl Stevens Status: New Priority: Normal Assigned to: Category: Self Service Password Target version: self-service-password-? Our web server is behind a HTTPS accelerator (HTTPS accelerator listens on public IP address, and forwards the unencrypted requests to the web server, which does not have a public IP address), and the code in sendtoken.php fails to guess the correct server URL (eg. instead of https://server.example.com/ssp/index.php, the URLs generated are http://192.168.x.y:80/ssp/index.php) The attached diff is a quick hack to allow the server admin to specify the $reset_url manually in the config file. I'm not sure if this is the 'correct' way to do it, but I don't know enough about PHP to do it any other way. This works for us, I figured someone else might find it useful. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________ ltb-dev mailing list ltb-dev@lists.ltb-project.org http://lists.ltb-project.org/listinfo/ltb-dev
