Overview
Artifact ID: | 72446a5dd3dfdbab10164c8450df80e42e94664afcd4b21090e32d374abd4911 |
---|---|
Ticket: | 44ec7f4c75ca9ef75dc9ed85cb9da4144e8eeb68
Add support for URIs |
User & Date: | js on 2022-10-02 18:04:11 |
Changes
- icomment:
Some more things that should be changed: * Normalization should strip leading `.` or `..` from paths. RFC 3986 specifies that a path of `/../foo` should be normalized to `/foo`, see [section 5.4.1](https://www.rfc-editor.org/rfc/rfc3986#section-5.4.1). * An empty authority should lead to an empty host and not a `n``l host, as a nil host would mean no authority. * The `file:` scheme should treat no authority the same way as an empty authority as per [RFC 8089 section 2](https://datatracker.ietf.org/doc/html/rfc8089#section-2). * Since `file:/some/path` is nicer to read to `file:///some/path`, it can be considered to switch using no authority instead of an empty authority when using `fileURIWithPath:`. * Since the `objfw-embedded:` scheme is not really hierarchical, it should be changed to not use an authority and not start paths with `/`, so that it can be treated as opaque.
- login: "js"
- mimetype: "text/x-markdown"