You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/01/10 22:13:01 UTC

[GitHub] [couchdb] kocolosk commented on issue #2369: Cluster to single node replication prints "Could not parse cookie from response headers cookie_format_invalid"

kocolosk commented on issue #2369: Cluster to single node replication prints "Could not parse cookie from response headers cookie_format_invalid"
URL: https://github.com/apache/couchdb/issues/2369#issuecomment-573225992
 
 
   Hi @m90 , thanks for this nicely detailed issue. As of #1462 (which landed in 2.2.0) the replicator will actually try to establish a session using cookie authentication. We made this change so that admins could crank up the work factor on authentication to protect against brute force attacks. So that explains why we're even talking about cookie-related code paths. The replicator will fall back to regular basic auth if it can't establish a session, so it makes sense that you're still seeing progress.
   
   As far as why the CouchDB 2.3.1 replicator thinks the cookie it's receiving from the target instance is invalid ... that I'm not so sure about. Is the single node target instance also running 2.3.1?
   
   If the log spam is getting to you and you just want the replicator to use basic auth you can change the `[replicator] auth_plugins` config setting on the cluster nodes:
   
   ```
   [replicator]
   auth_plugins = couch_replicator_auth_noop
   ```
   
   See http://docs.couchdb.org/en/stable/config/replicator.html#replicator/auth_plugins for the config documentation.
   
   /cc @nickva 

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services