sensiblearts opened a new issue, #5343: URL: https://github.com/apache/couchdb/issues/5343
I just (Nov 25) upgraded to CouchDb 3.4.2 on Ubuntu. It was working fine but the most upgrade broke it. I'm using CORS and sending headers, `Accept, Content-Type, Access-Control-Allow-Origin, X-Auth-CouchDB-Token, X-Auth-CouchDB-UserName, X-Auth-CouchDB-Roles`, where the username and token allow the user to access his own database. (I'm not using couch_per_user -- I'm doing that myself in the application layer.) Any ideas where to start looking? My original local.ini file is intact, unchanged by the upgrade. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
