Include third digit in the octet too #435
Conversation
| @@ -74,7 +74,7 @@ def self.connect_string_to_hash( str ) | |||
| # URI defined in RFC3986 | |||
| # This regexp is modified to allow host to specify multiple comma separated components captured as <hostports> and to disallow comma in hostnames. | |||
| # Taken from: https://github.com/ruby/ruby/blob/be04006c7d2f9aeb7e9d8d09d945b3a9c7850202/lib/uri/rfc3986_parser.rb#L6 | |||
| HOST_AND_PORT = /(?<hostport>(?<host>(?<IP-literal>\[(?:(?<IPv6address>(?:\h{1,4}:){6}(?<ls32>\h{1,4}:\h{1,4}|(?<IPv4address>(?<dec-octet>[1-9]\d|1\d{2}|2[0-4]\d|25[0-5]|\d)\.\g<dec-octet>\.\g<dec-octet>\.\g<dec-octet>))|::(?:\h{1,4}:){5}\g<ls32>|\h{1,4}?::(?:\h{1,4}:){4}\g<ls32>|(?:(?:\h{1,4}:)?\h{1,4})?::(?:\h{1,4}:){3}\g<ls32>|(?:(?:\h{1,4}:){,2}\h{1,4})?::(?:\h{1,4}:){2}\g<ls32>|(?:(?:\h{1,4}:){,3}\h{1,4})?::\h{1,4}:\g<ls32>|(?:(?:\h{1,4}:){,4}\h{1,4})?::\g<ls32>|(?:(?:\h{1,4}:){,5}\h{1,4})?::\h{1,4}|(?:(?:\h{1,4}:){,6}\h{1,4})?::)|(?<IPvFuture>v\h+\.[!$&-.0-;=A-Z_a-z~]+))\])|\g<IPv4address>|(?<reg-name>(?:%\h\h|[-\.!$&-+0-9;=A-Z_a-z~])+))?(?::(?<port>\d*))?)/ | |||
| HOST_AND_PORT = /(?<hostport>(?<host>(?<IP-literal>\[(?:(?<IPv6address>(?:\h{1,4}:){6}(?<ls32>\h{1,4}:\h{1,4}|(?<IPv4address>(?<dec-octet>[1-9]\d|1\d{3}|2[0-4]\d|25[0-5]|\d)\.\g<dec-octet>\.\g<dec-octet>\.\g<dec-octet>))|::(?:\h{1,4}:){5}\g<ls32>|\h{1,4}?::(?:\h{1,4}:){4}\g<ls32>|(?:(?:\h{1,4}:)?\h{1,4})?::(?:\h{1,4}:){3}\g<ls32>|(?:(?:\h{1,4}:){,2}\h{1,4})?::(?:\h{1,4}:){2}\g<ls32>|(?:(?:\h{1,4}:){,3}\h{1,4})?::\h{1,4}:\g<ls32>|(?:(?:\h{1,4}:){,4}\h{1,4})?::\g<ls32>|(?:(?:\h{1,4}:){,5}\h{1,4})?::\h{1,4}|(?:(?:\h{1,4}:){,6}\h{1,4})?::)|(?<IPvFuture>v\h+\.[!$&-.0-;=A-Z_a-z~]+))\])|\g<IPv4address>|(?<reg-name>(?:%\h\h|[-\.!$&-+0-9;=A-Z_a-z~])+))?(?::(?<port>\d*))?)/ | |||
There was a problem hiding this comment.
🤔 I see that <dec-octect> is trying to ensure the number is in the range 1–255, but is that necessary? Should it be simplified to \d{1,3}?
If I'm reading correctly, without this change, the number 134 is matching the first alternative, [1-9]\d, producing only two digits.
There was a problem hiding this comment.
Using \d{1,3} probably increases readability but incorrect in terms of correctness of IP address, so i don't know 🤷♂️
There was a problem hiding this comment.
As written in a9ad5eb the root cause was that there was no end-of-string anchor.
There was a problem hiding this comment.
Should it be simplified to \d{1,3}?
I'd like to keep the Regex as much as possible like where it comes from: https://github.com/ruby/ruby/blob/be04006c7d2f9aeb7e9d8d09d945b3a9c7850202/lib/uri/rfc3986_parser.rb#L6
There was a problem hiding this comment.
With the proposed fix the Regex jumps to the next possibility which is a reg-name, what means it is recognized as a regular hostname instead of an IPv4address.
Hi there,
When using connection string without hostaddr last digit in last octet of IP address goes away.
For example,
postgresql://user:pass@10.11.12.134 -> postgresql://user:pass@10.11.12.134?hostaddr=10.11.12.13Here is the fix for this behaviour