I'm marking this Fix Released and this seems to have been fixed
upstream, hence, should be fixed in quantal
** Changed in: maas (Ubuntu Quantal)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maa
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/975462
Title:
add ability to use over https
To manage notifications abo
** Changed in: maas
Status: Triaged => Fix Released
** Changed in: maas
Status: Fix Released => Fix Committed
** Changed in: maas (Ubuntu Precise)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
You're right, I had forgotten about those.
** Changed in: maas
Status: Invalid => Triaged
** Changed in: maas
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchp
I would disagree-- see 'grep -r 'http://%s' ./*' in toplevel source (as
an example). 'http://' is hardcoded in several places.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/975462
Title
This is a packaging issue - Apache handles all SSL not maas.
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/975462
Title:
add ability
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/975462
Title:
add ability to use over https
To manage notifications ab
