Actions
User story #3877
closedEnable HTTP/S by default
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
We should enable HTTP/S by default on Rudder 2.8
Updated by Matthieu CERDA over 11 years ago
We had with JCL quite a long discussion about that, that I am going to summarize here for future reference:
- We would like to remove the rudder-default vhost as its name is misleading in case of mixed SSL/non-SSL configuration
- We would like to add the "rudder-non-ssl" and "rudder-ssl" vhosts, stubs containing vhost type only declaration ( SSL settings, and / or rewriting rules )
- We would like to add the /opt/rudder/etc/apache2/rudder.conf file, containing the common configuration of the 2 vhosts.
Additionnaly, the packaging should take care of changing existing installations to use this new vhost configuration.
When we will have tested this solution enough, the 2.4 will receive a documentation about the manual installation of this configuration to get HTTP/S on this version too.
Updated by Matthieu CERDA about 11 years ago
- Status changed from 12 to Pending release
All merged, pending release !
Updated by Vincent MEMBRÉ about 11 years ago
- Subject changed from Enable HTTP/S by default on Rudder 2.8 to Enable HTTP/S by default
Updated by Vincent MEMBRÉ about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~beta1, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-October/000056.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog28
- Download information: http://www.rudder-project.org/foswiki/Download/
Actions