I think this is an expected behavior because your SSL certificate is probably for s1.mysite.com. When www.s1.mysite.com is requested the host name does not match with the certificate common name, hence the warning. You should be able to workaround this by getting a certificate that contains both common...