Hans Ginzel

Thank you! It seems, there is probably a bug. If password contains space, it is not quoted or percent encoded, e.g postgresql://username:"long password"@host:port/database. RFC3986 deprecates using quotes but my experience is that they mostly work well.

Thank you! It seems, there is probably a bug. If password contains space, it is not quoted or percent encoded, e.g postgresql://username:"long password"@host:port/database. RFC3986 deprecates using quotes but my experience is that they mostly work well.

Thank you! It seems, there is probably a bug. If password contains space, is not quoted or percent encoded, e.g postgresql://username:"long password"@host:port/database. RFC3986 deprecates using quotes but my experience is that they mostly work well.

Thank you! It seems, there is probably a bug. If the password contains space, is not quoted or percent encoded, e.g postgresql://username:"long password"@host:port/database. RFC3986 deprecates using quotes but my experience is that they mostly work well.

Thank you! It seems, there is probably a bug. If the password contains space, is not quoted or percent encoded, e.g postgresql://username:"long password"@host:port/database. RFC3986 deprecates using quotes but my exleriance is that they mostly work well.

Thank you! It seems, there is probably a bug. If the password contains space, is not quoted or percent encoded, e.g postgresql://username:"long password"@host:port/database. rfc3986 deprecates using quotes but my exleriance is that they mostly work well.

Thank you for lot features that KeePass supports. I fill url without user name and password, e.g. postgresql://host:port/database. Or should I fill there username and password too? How can I copy url with username and password filled to paste it into db client? E.g. postgresql://username:password@host:port/database. Or only with username in some cases? I am using KeePass 2.4.5. Thank you in advance.