+ in queryString not decoded correctly about flurl HOT 3 CLOSED

Great catch. It turns out that the method I used to decode the URL has a glitch specific to the + character that has been blogged about by Rick Strahl and others. I will provide an update soon, most likely going with Rick's method. Thanks for reporting.

from flurl.

This is fixed almost to your liking.

1. When parsing a query string, Flurl now interprets + as a space.
2. When encoding a query string, Flurl by default encodes spaces as %20, but Url.ToString now optionally takes an encodeSpaceAsPlus argument so you can control it.

The only thing you don't get here is preserving the original intent, i.e. if it goes in as a + it should come out as a +. Flurl stores unencoded values and encodes as needed, and re-architecting it to remember the original encoding seemed like a large effort without much benefit. Servers will be perfectly happy with %20 if you're making HTTP calls, and if you want +'s for vanity you've got the ToString overload. Hope this a satisfactory resolution.

Both Flurl and Flurl.Http have been upgraded with this change on NuGet.

from flurl.

Sounds good :-)

from flurl.