nickva commented on issue #1851: URL: https://github.com/apache/couchdb/issues/1851#issuecomment-2868293109
Thanks for reaching out @peterfarrell. It's interesting that the replication still worked. But it does make sense based on the behavior of the replicator. When in the response from the endpoints it sees a new cookie, it will assume it's a refreshed cookie sent by the CouchDB, and it will attempt to parse it (to get the max age) and start using the new cookie. However, if it can't parse it, it will emit an error (to let the user know) and continue. I guess eventually when the cookie expired, the real cookie from CouchDB endpoints makes it to the replicator, otherwise the replication would stop working eventually? It's great you found a solution to stop the generation of log errors. Another potential fix might be to disable cookie authentication and use basic auth for the replicator. https://docs.couchdb.org/en/stable/config/replicator.html#replicator/auth_plugins ```ini [replicator] auth_plugins = couch_replicator_auth_noop ``` The downside there is with the upgrade to a stronger hash (kdf) function each request will take longer. So your solution to disable the extraneous cookie is preferable. -- 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]
