-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

you seem to have two separate problems:

We have bought wild card ssl certificate *.xyz.com
Now the problem is when the user hits with xyz.com we get invalid certiciate. but if we hit through www.xyz.com it is working fine.

I used the read write module to redirct all the xyz.com request to www.xyz.com but https://xyz.com does not work properly.

1. As far as I know, the name "xyz.com" doesn't match the expression "*.xyz.com". So I'd expect that the browser would issue a warning when you go to https://xyz.com/ and are presented this wild card certificate. For the same reason the certificate should work fine with "www.xyz.com" and with "secure.xyz.com" and with "whatever.xyz.com". (Compare to file-based wildcard matching. A file called BLAH won't match "*.BLAH", but a file called "WHATEVER.BLAH" will.)

2. As for mod_rewrite: you'd have to post the configuration and a more thorough description of what doesn't work properly before others can comment..

- --
Best regards / met vriendelijke groet, Karel Kubat



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkmTGMYACgkQ23FrzRzybNVFawCgoM4q6YwB5bWcU77Cb+kVwyym
fqQAnR1vx23gY86+/pz5zFSd3uJHaGxc
=5HMb
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
  "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Reply via email to