Was there any confusion about the plugin creating an HTTPS capability where one doesn't exist? I always understood the outcome to be very clear.