I've failed to reproduce this on Lucid. http://127.0.0.1/server-status works for me. I also installed apache2 on Hardy, verified that server-status works, upgraded to Lucid and verified that it still works.
Please can you explain why you think this is a bug, rather than a configuration issue on your system? Have you tried using https as the error message describes? If this is a configuration issue, there are pointers to get help here: http://www.ubuntu.com/support/community.
Since it seems likely that this is a configuration issue related to your upgrade and related SSL configuration, and not a bug, I'm marking this bug as Invalid.
If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, including steps to reproduce, and then change the bug status back to New.
Thank you for your report.
I've failed to reproduce this on Lucid. http:// 127.0.0. 1/server- status works for me. I also installed apache2 on Hardy, verified that server-status works, upgraded to Lucid and verified that it still works.
Please can you explain why you think this is a bug, rather than a configuration issue on your system? Have you tried using https as the error message describes? If this is a configuration issue, there are pointers to get help here: http:// www.ubuntu. com/support/ community.
Since it seems likely that this is a configuration issue related to your upgrade and related SSL configuration, and not a bug, I'm marking this bug as Invalid.
If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, including steps to reproduce, and then change the bug status back to New.