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/13 19:49:05 UTC

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

nickva edited a comment 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-573838817
 
 
   @m90 
   
   1) Could you capture the responses from the client to the proxy, then from the proxy to CouchDB see anything is adding cookie. Also notice if there are any differences at all between "Set-Cookie" headers before and after the proxy.
   
   2) Just to debug the scenario, can you eliminate the nginx proxy from the connection chain altogether, by say having a local cluster or use an SSH tunnel. Then see if errors persist or not.
   
   Based on the logic in the code https://github.com/apache/couchdb/blob/1347806d2feebce53325070b475f9e211d240ddf/src/couch_replicator/src/couch_replicator_auth_session.erl#L462-L464 it looks like there was a cookie found _but_ it doesn't have an "AuthSession" part. That looks like a bug as CouchDB should ignore that cookie altogether and only pay attention to the ones having an "AuthSession" instead of failing nosily. However before making that change, let's see if we can confirm that theory.

----------------------------------------------------------------
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