Eric S. Johansson wrote: >> > And what does onlysecure mean? >> >> It is a key to only allow access from secure connections. It >> implements a mechanism to switch the protocol on-the-fly (actually, >> it is pretty cool) but AFAIK it is still unsupported by the Mozilla >> browsers; I don't know if any of the other ones knows about it. >> >> In the worst case, you can use it to only allow secure connections >> to those resources. >> > > cool. simplest method I've seen for turning on ssl yet. but I found a > problem. I'm using squirrel Mail on a nonstandard port and I want SSL > on that nonstandard port. it worked before I used secure only so I know > everything is functional from a serving perspective. now, when I make > the https request, it just sits there spinning its little circle and I > get nothing in the log. If I revert back to straight http, I get a 426 > upgrade required error message.
Yeah, that is because the connection upgrade is not supported by the browser. By the way, your request about supporting non standard ports for the https server makes sense. I have committed a new patch to add a new configuration option to set it: === Port 80 PortTLS 443 === It will be included on 0.4.28 next week. :-) > on a related theme, If I want to have a different certificate for a > virtual host, would I redefine the certificate definitions in the > virtual server definition? could I do that within the virtual > server definition? Yep, you can use SSLCertificateFile, SSLCertificateKeyFile and SSLCAListFile inside the virtual hosts structures. > and completely unrelated but necessary, webdav? is it supported yet? > Or is that bounty material? It is not supported. I thought about making a bounty of it, but I am not sure about it is really worth the effort. Do people use WebDAV, is it really an important feature to be implemented? -- Greetings, alo. _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
