You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Between 0.5 and 0.8, we had #749 raised and had to percent-encode each querystring parameter. As explained there, since ngx.encode_args does not percent-encode some characters, we had to go with LuaSocket's url.escape, which is defined like this:
function_M.escape(s)
return (string.gsub(s, "([^A-Za-z0-9_])", function(c)
returnstring.format("%%%02x", string.byte(c))
end))
end
Meaning it will also encode the (although unreserved) . character.
Tbh, I think your backend application should always be prepared to percent-decode querystring values anyways, since those can contain reserved characters.
On 0.8.3 (upgrading from 0.5.4) the query parameters get url encoded
After upgrading to 0.8.3 from 0.5.4 I noticed that a url that is returned by our api gets encoded by kong. Is there a reason for the change?
Steps To Reproduce
Result contains:
Result contains:
The text was updated successfully, but these errors were encountered: