Can't Connect With Special Characters in Mysql Password

[wstewarttennes]

Not able to connect with special characters or replacing special characters in the password field with their % representation.

[jorgerojas26]

Ok, i'll check this. Thanks for the issue.

[jorgerojas26]

I found a solution for this. It was just a matter of escaping the url string correctly.

I will make a PR soon.

[pixelskull]

Not quite sure if it is related to this, when trying to connect to a postgres database I get the error that it could not parse the url:

pg://user:pass@localhost/db_name?sslmode=disable

parse "pg://user:pass@localhost%2Fdb_name?sslmode=disable": invalid URL escape "%2F"

the %2F is obviously the escaped "/". It seems that encoding with the net/url package does not like the schema.

[jorgerojas26]

Not quite sure if it is related to this, when trying to connect to a postgres database I get the error that it could not parse the url:

pg://user:pass@localhost/db_name?sslmode=disable

parse "pg://user:pass@localhost%2Fdb_name?sslmode=disable": invalid URL escape "%2F"

the %2F is obviously the escaped "/". It seems that encoding with the net/url package does not like the schema.

The URL encoding/decoding is done internally, please try with the raw connection url string, without the escaped "/".

[pixelskull]

Oh sorry, the quote from the earlier post is my input. I entered it without escape, but after saving it seems to be escaped.
Just to be clear, this is my input: pg://user:pass@localhost/db_name?sslmode=disable

[jorgerojas26]

Ok, the problem here is that it is not parsing correctly your input because of the /db_name, if i put the url without the "/db_name" it works correctly.

I'll work on that.

[pixelskull]

Thanks for your effort. I am stroked to use this awesome project :)

[jorgerojas26]

I'm thinking of reverting the changes i made to do the escaping internally, this adds a lot of unnecessary complexity that could be avoided if the users just escape their connection strings.

I'm working on it, so we can move on to develop other features.

[pixelskull]

Since the fix was working for passwords, you could slice the user and password section, and use the escaping only for this part. There shouldn't be a case for the url part to be escaped, since every occurrence of a special character here will break the url?!