New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling HTTPS logins doesn't work for non standard port (Trac #866) #866
Comments
trac user kevin_traas wrote on 39425728-11-10 I ran into the same issue setting things to use HTTPS - even though I'm running on standard 443/tcp. The only problem I've found so far has been on the login page, which I fixed as per the following diff: Change line 27 of /var/www/views/default/account/forms/login.php: From: if ((isset($CONFIG->https_login)) && ($CONFIG->https_login)) To: if ((isset($CONFIG->https_login)) && ($CONFIG->https_login) && !ereg('https', $login_url)) Solved my problem! |
trac user kevin_traas wrote on 39425731-06-17 Replying to kevin_traas: On second thought.... the better solution might be to use eregi(), not ereg(). So, as follows: To: if ((isset($CONFIG->https_login)) && ($CONFIG->https_login) && !eregi('https', $login_url)) |
brettp wrote on 40085195-09-20 Anyone know the status of this? |
Milestone changed to |
cash wrote on 40146951-03-29 Here is the complete status on this:
All of the above are simple changes that we can wait for 1.8 to handle. |
cash wrote on 40861103-05-22 (In [svn:7281]) Refs #866 - registration uses https if configured for login |
Milestone changed to |
Milestone changed to |
Milestone changed to |
Solution is to not use the https login feature and just specify the port in your wwwroot, serving the whole site over https. |
Original ticket http://trac.elgg.org/ticket/866 on 39193405-01-22 by codebrane, assigned to unknown.
Elgg version: 1.5
1.5 RC2
If you enable HTTPS logins from the installer, you can never login if you have a non standard SSL port. There's no way to specify the port from the installer. If you prepend https:// to the site url in the installer, the site becomes httpss://
The text was updated successfully, but these errors were encountered: