Re: [go-nuts] Re: url.parse issue if the first character of a url is a number

2019-02-12 Thread mikioh . public . networking
if you are talking about https://play.golang.org/p/0oIfvatzysI, it's better to file an issue. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubsc

Re: [go-nuts] Re: url.parse issue if the first character of a url is a number

2019-02-12 Thread Shulhan
On Tue, 12 Feb 2019 09:35:38 -0800 (PST) jake6...@gmail.com wrote: > I can not speak directly to Go's version, but according to the IETF > standards, a domain name can not start with a digit. So they are in > fact malformed. > It used to, but then RFC 1123 section 2.1 relaxed the syntax to all

[go-nuts] Re: url.parse issue if the first character of a url is a number

2019-02-12 Thread jake6502
I can not speak directly to Go's version, but according to the IETF standards, a domain name can not start with a digit. So they are in fact malformed. On Sunday, February 10, 2019 at 9:23:54 PM UTC-5, Nathan Xu wrote: > > What I said is the url content without http/https . > > On Sunday, Febr

[go-nuts] Re: url.parse issue if the first character of a url is a number

2019-02-10 Thread mailme . xu
What I said is the url content without http/https . On Sunday, February 3, 2019 at 4:09:05 PM UTC+8, Tamás Gulácsi wrote: > > An url must start with a scheme (i.e. http://). -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from th