Flurl.Http v3.0.0 Release Notes
Release Date: 2019-09-13 // over 5 years ago-
๐ Flurl 3.0 contains a major rewrite of the URL building/parsing engine. It brings
Flurl.Url
's feature set more in line withSystem.Uri
, while also addressing some of its quirks.๐ New Features
๐ New
Url
properties (#440)Scheme
(read/write)UserInfo
(read/write)Host
(read/write)Port
(read/write)Authority
(read-only,UserInfo
+Host
+Port
)Root
(read-only,Scheme
+Authority
)PathSegments
(modifiable)IsRelative
(read-only)
-
IsSecureScheme
(read-only, true for https or wss)๐ All URL-building extension methods currently on
string
now available onSystem.Uri
(#489)๐ New fluent builder methods on
Flurl.Url
,System.Uri
, andstring
:RemovePathSegment()
(removes the last segment)RemovePath()
RemoveQuery()
-
Reset()
(restoresUrl
to its original state as constructed, NOT available onstring
)๐ Support for relative URLs (#407)
Parameterless constructor for
Url
(#518)๐ New static utility method:
Url.ParsePathSegments(string)
(assumes entire string is the path portion of a URL)๐ฅ Breaking Changes from 2.x
- ๐ New collection type for
Url.QueryParams
(#555) Url.Path
changed to be more in line with the formal definition. Previously it included everything (scheme, host, etc.) up to the query string. It now starts after the host/port, including the leading/
if present.Url.IsValid()
instance method was removed. It was confusing in the case of relative URLs since arguably any string could be considered a valid relative URL. Check theIsRelative
property instead. (StaticUrl.IsValid(string)
method is still available but, same a before, returns true only for valid absolute URLs.)- โฌ๏ธ Dropping support for older platforms (#544)
๐ Bug fixes:
Url.ToUri()
now works for relative URLs (#407)
Previous changes from v2.8.2
-
- ๐ Bug when decoding encoded
+
(#437)
- ๐ Bug when decoding encoded