* Open site in browser doesn't detect the vhost is an https:// one not a
http:// - FIXED
* The debian standard location for ssl certs seems to be /etc/apache2/ssl
- verify it's true
- use that as default for certs. - FIXED
* we are using the sitename/servername as the basis for .key and .pem naming.
we should make sure a certificate with the same name doesn't already exists. if
so let's make a sitename_2 one.
Certs are site name / date stamp to keep then unique
** Changed in: rapache
Status: New => In Progress
--
Rapache SSL glitches
https://bugs.launchpad.net/bugs/258063
You received this bug notification because you are a member of Rapache
Developers, which is subscribed to Remote Apache Management tool .
Status in rapache: In Progress
Bug description:
SSL plugin works nicely but we have a few glitches:
* Open site in browser doesn't detect the vhost is an https:// one not a
http://
* SSL stuff doesn't work on vhost creation.
* The debian standard location for ssl certs seems to be /etc/apache2/ssl
- verify it's true
- use that as default for certs.
* apache complains if *:80 and *:*/* VirtualHosts and NameVirtualHosts are
mixed. so we need to prompt the user and convert the vhosts on the fly
* we are using the sitename/servername as the basis for .key and .pem naming.
we should make sure a certificate with the same name doesn't already exists. if
so let's make a sitename_2 one.
_______________________________________________
Mailing list: https://launchpad.net/~rapache-devel
Post to : [email protected]
Unsubscribe : https://launchpad.net/~rapache-devel
More help : https://help.launchpad.net/ListHelp
