Hi Conor, I've had issues with CouchDB's HTTPS in general. Same type of symptoms : curl works OK, browsers don't. I thought it might be specific to self-signed SSL certificates, but I never tried with a regular certificate. Anyway, a previous email on this mailing list hinted that CouchDB's Erlang implementation of SSL may be buggy. The suggestion was to use a HTTP<->HTTPS proxy in front of the CouchDB, such as stunnel. Here's a "self-solved" issue on StackOverflow : http://stackoverflow.com/questions/30939983/couchdb-over-https-and-self-certified-certificate-browsers-reject-it
Regards Foucauld 2015-09-16 11:51 GMT+02:00 Conor Mac Aoidh <[email protected]>: > Hi yes, 'enable_cors' is set to true. I think it could be a server > configuration problem as couchdb config looks ok. > > Thanks > > Conor > > > On 15/09/15 17:25, Aurélien Bénel wrote: > >> Hi Conor, >> >> ➜ curl -X GET https://example.com:6984/_config/cors >>> >> Should we assume you also set `enable_cors`? >> >> [httpd] >> enable_cors = true >> >> >> Regards, >> >> Aurélien >> > >
