Message-ID: <gh-pgjdbc-pgjdbc-2694-c2672441737@github.com>
From: "fladi (@fladi)" <noreply+fladi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 20 Feb 2025 19:13:55 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2694: the url is invalid
In-Reply-To: <gh-pgjdbc-pgjdbc-2694@github.com>
References: <gh-pgjdbc-pgjdbc-2694@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: fladi
X-GitHub-Comment-Id: 2672441737
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2694
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2694#issuecomment-2672441737
Content-Type: text/plain; charset=utf-8

I was hit by the same issue, our databases follow the convention:

- `vhost-1.example.com/production`
- `vhost-1.example.com/testing`
- `vhost-1.example.com/feature-1234`
- `vhost-2.example.com/production`
- ...

Now someone wants to connect to them via JDBC (42.7.5) and is hit with `Unable to parse URL jdbc:postgresql://db.example.com:5432/vhost-1.example.com/testing`. I tried to use RFC3986 as stated in the documentation but this only resulted in the same error (with `%2F` decoded to "`/`").

JDBC was used within DBeaver.