Please provide a runnable sample to demonstrate what you did. Thank you

@davecheney

package main

import (
	"net/url"
	"fmt"
)

func main() {
	oriqueryForm0, err0 := url.ParseQuery(`http://192.168.240.36:3000/nnrf-disc/v1/nf-instances?service-names=  &requester-nf-instance-fqdn=seliiu`)
	if err0 == nil {
	    fmt.Printf("service names = %s", oriqueryForm0["service-names"])
	}
}

//The code above should not print anything out because of the space char behind "service-names="

Thank you for your sample code, why do you believe that the space should terminate the URL? Do you have an example where a browser or client send this URL?

@davecheney
According to RFC 3986, space characters should not be allowed in URLs.
In most cases, browsers will translate space characters to %20 or terminate the request.
In some applications(such as bare metal embedded systems) where clients are not using a browser and there is no validation check for the URL, then the server will not be able to detect the error in the URL if the incoming request URL is used as an argument for parseQuery
I used a simple HTTP2 client & server demo code I found on the internet and verified the behavior. Please let me know if you are interested in seeing the code.

cc @bradfitz

@pp5311006 i think this is a question of where the url comes from. It is not possible for a URL with a space in it to be transmitted by HTTP. The space could be present if the url was stored in a database or file or read via input. This sounds like an input validation problem, but equally given the problems this could cause maybe ParseQuery could be stricter about the input it accepts.

@davecheney
You are right. I would love to see ParseQuery function having a stricter input validation check.
Currently we are trying to prevent this problem by doing extra validation check, it would be nice to have it in ParseQuery by default.