Securing WIFI for a web application
couchdb, jquery, security, ssl, wifi
Solution
The design of your CORS-enabled application is not directly related to whether it uses SSL. See this section of the CORS specification.
Designing your application to support CORS and serving your application over an SSL connection are separate decisions and might not even be made by the same people. When you say "installed and run under different LANs", I assume you mean that different people/companies will host your server-side code, possibly under different domains.
You should not even assume that the web server hosting your code is the same as the web server doing the SSL, as the SSL termination might be a different device that then proxies requests back to the web server.
What I would do in a case like this document the potential need for SSL in your installation instructions and let people do it (or not) in a way that's appropriate to their environment.
Problem
I have created a CORS web application (only javascript), where I want to be installed and run under different LANs. I'd like to put SSL, but I don't know what the exact configuration of the lan will be and probably it will be different every time. So I think I can't add a certified SSL. Is there any possible other solution with SSL? I don't like the approach of adding an uncertified SSL because of the warnings. How else can I encrypt the packages and make secure authentication of the requests? I am using CouchDB default CORS but the packages can be sniffed if the web application is installed and used in an open WIFI. The application is using only javascript and I don't know how I can protect it (the only backend is the storage in the couchDB).