Closed jsiefer closed 1 year ago
Are you sure? I see everywhere that _
are prohibited
url
crate seems to accept _
indeed:
let is_invalid_host_char = |c| {
matches!(
c,
'\0' | '\t'
| '\n'
| '\r'
| ' '
| '#'
| '/'
| ':'
| '<'
| '>'
| '?'
| '@'
| '['
| '\\'
| ']'
| '^'
| '|'
)
};
I think this part caused problems for me - inside the parsing function for ClientSettings
Yes but I used the url
crate as a reference to know if underscores were actually supported because everywhere I see says otherwise
You are right. Looks like underscores are not allowed in domain names. I only stumbled on it when I was using docker and used an underscore in the service name.
Should (can) parsing fail then instead of falling back to default values?
Hey @jsiefer,
PR #169 supports underscore in hostname and gossip seeds and also fixes the issue you mentioned.
thank you!
Can we allow underscore _ for host names when parsing settings string? Quite commonly used when using docker compose i think.
e.g.
esdb://foo:bar@eventstore_db:2113