2022-10-11
| ||
00:23 | • Fixed ticket [44ec7f4c75]: Add support for URIs plus 4 other changes artifact: ebc6c953a2 user: js | |
2022-10-03
| ||
19:57 | • Ticket [44ec7f4c75]: 3 changes artifact: 869dce6b19 user: js | |
00:47 | • Ticket [44ec7f4c75]: 3 changes artifact: 8e35b34057 user: js | |
2022-10-02
| ||
18:04 | • Ticket [44ec7f4c75]: 3 changes artifact: 72446a5dd3 user: js | |
2022-09-28
| ||
22:13 | • Ticket [44ec7f4c75]: 3 changes artifact: c55e4c05d1 user: js | |
19:37 | • Ticket [44ec7f4c75]: 4 changes artifact: 6b33ad93e7 user: js | |
2022-09-27
| ||
23:36 | • New ticket [44ec7f4c75]. artifact: c474b13923 user: js | |
Ticket UUID: | 44ec7f4c75ca9ef75dc9ed85cb9da4144e8eeb68 | |||
Title: | Add support for URIs | |||
Status: | Fixed | Type: | Enhancement | |
Severity: | Severe | Priority: | High | |
Subsystem: | Resolution: | Fixed | ||
Last Modified: | 2022-10-11 00:23:29 | |||
Version Found In: | Milestone: | 1.0 | ||
User Comments: | ||||
js added on 2022-09-27 23:36:28:
Currently, It seems the main changes needed would be:
As this is breaking the API, this needs to happen before the 1.0 release. js added on 2022-09-28 19:37:13: This raises the question: What to do with URLs know how to locate something, but URIs don't. But theoretically a handler could even know how to retrieve it without a location, hence js added on 2022-09-28 22:13:40: Renaming Dropping fragment was obviously a brain fart. What I meant was dropping js added on 2022-10-02 18:04:11: Some more things that should be changed:
js added on 2022-10-03 00:47:36: URI parsing is now implemented ([c75059a52f]), as well as not using However, parsing of relative URIs is not according to RFC 3986 yet. js added on 2022-10-03 19:57:37:
This means only the normalization and handling of relative URIs needs to be changed to comply with RFC 3986. js added on 2022-10-11 00:23:29: Relative URIs as per RFC 3986 have been implemented in [3b2697b2a7]. This completes URI support. |