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
When trying to urlEncode a perfectly reasonable string containing newlines (%0a), they are encoded as %a which is incorrect and isn't properly parsed by other clients.
This is also affecting tabs. Other non-printables are probably unlikely to be used in URL encoding.
In my case I was trying to encode a multi-line string to place in a fragment for a link to translate.google.com. When properly encoded it happily accepts these strings.
Added reserve() calls in urlEncode/urlDecode that should improve memory management in certain situations (e.g. for ascii field names and numeric values in query strings).
When trying to urlEncode a perfectly reasonable string containing newlines (%0a), they are encoded as %a which is incorrect and isn't properly parsed by other clients.
This is also affecting tabs. Other non-printables are probably unlikely to be used in URL encoding.
In my case I was trying to encode a multi-line string to place in a fragment for a link to translate.google.com. When properly encoded it happily accepts these strings.
I suppose the problem is here:
https://github.com/rejectedsoftware/vibe.d/blob/c8a03f93639ada7a307ea7dd3db0db909275a646/source/vibe/textfilter/urlencode.d#L44
-[Unknown]
The text was updated successfully, but these errors were encountered: