AstraLuma opened a new issue, #5223:
URL: https://github.com/apache/couchdb/issues/5223

   ## Description
   
   It looks like there's a bug in URL manipulation with regard to IPv6 
addresses.
   
   A snippet from `/_scheduler/jobs`:
   ```
       {
         "database": "_replicator",
         "id": "3e9e019d74f393c8fb8319dd43abec45+continuous",
         "pid": null,
         "source": "http://[fdaa:a:d05:a7b:12:eb5a:cc23:2]:5984/_users/";,
         "target": "http://localhost:5984/_users/";,
         "user": null,
         "doc_id": "pup_fdaa:a:d05:a7b:12:eb5a:cc23:2__users",
         "info": null,
         "history": [
           {
             "timestamp": "2024-09-06T03:45:14Z",
             "type": "crashed",
             "reason": "{replication_auth_error,\n    
{session_request_failed,\"http://fdaa:a:d05:a7b:12:eb5a:cc23:2/_session\",\n    
    \"admin\",\n        {url_parsing_failed,{error,invalid_uri}}}}"
           },
   ```
   
   Note that the `_session` URL does not show the requisite `[]` around the IP 
address.
   
   ## Steps to Reproduce
   
   1. Set up two CouchDB instances on an IPv6 network
   2. Configure them to replicate with each other, referring to the other by IP 
address
   
   ## Expected Behaviour
   
   Replication happens cleanly.
   
   ## Your Environment
   
   ```
   {
     "couchdb": "Welcome",
     "version": "3.3.3",
     "git_sha": "40afbcfc7",
     "uuid": "2ec4265a1ffc0f5d75390407dd3cd392",
     "features": [
       "access-ready",
       "partitioned",
       "pluggable-storage-engines",
       "reshard",
       "scheduler"
     ],
     "vendor": {
       "name": "The Apache Software Foundation"
     }
   }
   ```
   
   ## Additional Context
   
   This was exposed while working on an automagic CouchDB on fly.io project.
   


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

Reply via email to