Support query parameters without encoding

[yangzhiw]

When calling the SetQueryParam method, the request request will encode the query in the URL, for example: registry=nacos://test:6801, which will be encoded as: registry=nacos%3A%2F%2Ftest%3A6801; is there any way? To set query parameters without encoding, for example: SetQueryEscape(false)

[jeevatkm]

@yangzhiw Thanks for reaching out. Without query escape, the URL may become broken. It is not recommended to do that. Ideally, the application/service endpoint receiving this parameter should unescape first before using it.

[ahuigo]

try to put unencoded query to url like this:

	url := ts.URL + "/post?un-escape=nacos://test:6801"
	resp, err := req.
		EnableTrace().
		SetQueryParams(map[string]string{
			"escape":"nacos://test:6801",
		}).
		Post(url)

//  curl -X POST 'http://127.0.0.1:51301/post?unescape=nacos://test:6801&escape=nacos%3A%2F%2Ftest%3A6801'

[antixcode6]

This is unfortunately something I have ran into recently as well.

Ideally, the application/service endpoint receiving this parameter should unescape first before using it

While I agree that they should Some APIs that I've been trying to consume recently refuse to un-encode the request on their end and will only accept raw, unencoded, query params. I believe giving the package consumer/programmer the option to decide this behavior makes more sense than relying on the service (which we most likely have no control over) to do the right thing.

[jeevatkm]

@antixcode6 I will add it in v3

[takanuva15]

I am interested in this functionality as well since I'm dealing with legacy servers that cannot handle escaped query parameters at the moment. Can we add a function SetEscapeQueryParams(bool b) into v2 just like we have SetJSONEscapeHTML currently? This would really help improve the flexibility of the client for different requests

[jeevatkm]

@takanuva15 Is it an urgent need? As you can see, I marked this issue for v3, which is currently in development.

[takanuva15]

@jeevatkm no it's not urgent; thanks for your quick reply

[jeevatkm]

@yangzhiw @antixcode6 @takanuva15 - I have implemented this in Resty v2, in the branch unescape-query-params. Can you try and share your testing feedback?