The mentioned PR treats the nats url as a single string and then parse it as if it is one url. The reality is multiple urls are supported there so this is simply not going to work
Further conceptually it tries to take the proxy path from the url - but as this supports multiple urls this just doesnt make sense
The right fix is for nats.go to get the proxypath behaviour per connection url rather than try to fix this here
The mentioned PR treats the nats url as a single string and then parse it as if it is one url. The reality is multiple urls are supported there so this is simply not going to work
Further conceptually it tries to take the proxy path from the url - but as this supports multiple urls this just doesnt make sense
The right fix is for nats.go to get the proxypath behaviour per connection url rather than try to fix this here