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
Request.segment and Target.segment encode literal . and .. values as
path data. Previously, resolution or libcurl could interpret a dynamic
identifier as current- or parent-directory navigation.
Relative target serialization preserves relative meaning for first segments
containing :, leading empty segments, and an appended empty segment. It adds
a dot prefix when needed instead of producing an absolute or scheme-relative
reference, or dropping the distinction between an empty segment and no path.
Relative fragments are percent-encoded on serialization, so spaces, #,
Unicode, and literal percent characters round-trip through target parsing.
Target.resolve removes literal dot segments from absolute target paths,
matching its behavior for nonempty relative paths and preserving encoded dots.
Compatibility
Public API signatures are unchanged. For intentional directory navigation,
use reference syntax such as target!"../users"; .segment ".." now always
supplies a literal path segment.
The package version and default user agent are now 0.3.1 and leanhttp/0.3.1.