View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005927||phpList 3 application||Interface - Backend||public||30-03-06 18:28||18-02-08 14:16|
|Target Version||2.10.7||Fixed in Version||2.10.3|
|Summary||0005927: https not natively supported|
|Description||When the system runs on a secure server (https://..), the admin backend does not work completely any more, due to hard-coded protocol informations in the source...|
Whenever you try to save things in the admin menue (configuration), you get forwarded to the hostname without https (just http).
As a quick hack, I grepped for the http and replaced it with https, where neccesary, but this is not elegant either :-)
I feel there is no need for hard-coding the protocol into the source, as php should have access to all the needed server-variables. Therefore, the target address could be constructed by the script, making it work on any server, http or https...
|Tags||No tags attached.|
if you can give me the files and line numbers that need to change, I'd happily do that, but otherwise it's a bit of a can of worms.
Maybe it's even quicker to set up an apache redirect that redirects the http to https, that's only one line.
I agree that it would be nice to support this, but there are loads of other things to sort out.....
I just grepped for "https" and found these files; actually, I don't know whether the "https" was in some of them before already...
(I already removed all occurances of "https" where I sure did not change anything in the file, e.g. the paypal-Link...)
||Here are the files I changed, but as I said: I just did a quick hack and replaced http with https...|
files.tar.gz (49,683 bytes)
||made most locations use a global variable, but it's initialised in "init.php" and not in config.php for now|