On Sat, 2003-11-08 at 13:44, Franki wrote:
I think you are not understanding what I mean..
Right now, I have the cert bound to my secure.my-domain.com subdomain..
I don't need the cert to work with any other domains...
I just want to create a way whereby I can give my users the ability to each use my secure.my-domain.com subdomain
to access their files. files via SSL..
What I was thinking was you could set up was a wild card that would work like: https://*.my-domain.com
Then each of the sites could have a cname to utilize your cert.
https://domain1.my-domain.com https://domain2.my-domain.com
etc....
Anyway, what happens if you symlink secure.my-domain.com/theirusername to the document root for their-domain.com?
Yeah, I understand wildcard certs.. but one would not make my job any easier for this task..
Funnily enough I did something similar to what you just suggested.
I have setup a "secure" webroot which contains one dir for each host..
The dirs are symlinked to the users web root.. like "cgi-ssl" so they can easily put stuff in those directories like normal.
seems to be working. but I'd have prefered a simplier answer..
no matter, It's working, that will do for now...
rgds
Franki
--
Please sign our petition to encourage notebook manufacturers to offer video card upgrades just like desktops.
http://www.petitiononline.com/inspiron/petition.html
For free scripts, online webmaster tools, HTML, XHTML, Perl & PHP tutorials and stuff, visit:
http://htmlfixit.com, Free web developer resources.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
