2.10.0
Three years into this major release, and I'm still finding new and exciting features of HTTP! Turns out, requests should not contain fragments, and the semantics about replacing fragments from the original url with the redirects' fragment are only relevant if the user agent wants to see the "final version" of the URL. Thus, minreq no longer sends the fragment in the request, and now responses have an url
field.
Fixed
- Fragment handling, once again. Turns out you're not supposed to include fragments in the request. This may break usage with servers that are written with the wrong assumptions. Thanks for the report, @rawhuul! (#100)
Added
Response::url
andResponseLazy::url
fields, to contain the final URL after redirects and fragment replacement semantics.