I've confirmed this is still an issue in cs:apache2 and is triggered if you're using the self-signed certificate option
I've confirmed this is still an issue in cs:apache2 and is triggered if you're using the self-signed certificate option