Flurl.Http 2.3.0

This release focuses on enhancements to exception handling:

• Less verbose FlurlHttpException.Message (#297)
• BREAKING: new FlurlParsingException, can be handled globally (#299)
• BREAKING: FlurlHttpException.GetResponseString & GetResponseJson replaced by async equivalents (#300)
• BREAKING: HttpCall.ErrorResponseBody removed (#300)
• Response string available on JSON parsing errors (#288)
• BUGFIX: Null ref exception in ShouldHaveCalled..WithContentType when body is empty (#285)

Flurl 2.7.1

• SetQueryParam with array should add multiple QueryParameters (#301, #276)
• Added public method QueryParamCollection.Merge (#301)

Flurl.Http 2.2.1

• WithHeader should exclude/remove header if value is null (#282)

Flurl.Http 2.2

• Add target for .NET Standard 2.0 (#267)
• Automatic decompression of GZIP and DEFLATE by default (#266)
• Fix to HttpTest for MSTest runner (#207)
• Remove TestFlurlClientFactory (#269)
• Bump Flurl dependency to 2.7
• Bump Json.NET dependency to 11.0

Flurl 2.7

• Add target for .NET Standard 2.0 (#267)
• Do not encode reserved characters on the name side of query name/value pair (#272)

Flurl.Http 2.1.1

• Up'd Flurl dependency to 2.6

Flurl 2.6

• BREAKING: Better URL encoding/decoding methods (#262)
• Fixed issue with spaces always encoding to + (#258)
• Re-fixed "URI too long" error with URL-encoded content (#185)

Flurl 2.5.2

• Avoid "Uri string is too long" error when possible (#185)
• Prevent double-enoding (#253)
• Optional fullyEncode arg added to AppendPathSegment (#253)

Flurl.Http 2.1.0

• BREAKING: FlurlHttp.ConfigureClient takes Action<FlurlClient> instead of Action<FlurlHttpSettings> (#247)
• BREAKING: DownloadFileAsync favors filename in Content-Disposition header over last URL segment when fileName arg isn't provided by user (#240)
• BREAKING: When DateTime or DateTimeOffset is passed as header value or URL-encoded content value, it is serialized to ISO 8601 (#249)
• Fixed a couple settings inheritance glitches (#239, #246)

Flurl 2.5.1

• BREAKING: Serialize dates to ISO 8601 when using DateTime or DateTimeOffset as values of query string params, etc (#249)
• A few null checks to prevent possible bugs