We haven't customized our Apache2 configuration at all Mike. We hit this issue on our prod environment and were able to recreate on a maas environment. http://<maas-ip-address>:5240 has been the work around that we've been using since the bug was opened. We have not seen this issue with 1.9.
We haven't customized our Apache2 configuration at all Mike. We hit this issue on our prod environment and were able to recreate on a maas environment. http://<maas-ip- address> :5240 has been the work around that we've been using since the bug was opened. We have not seen this issue with 1.9.