💾 Archived View for rawtext.club › ~sloum › geminilist › 004785.gmi captured on 2024-02-05 at 11:18:31. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
easrng easrng at gmail.com
Fri Jan 8 16:42:46 GMT 2021
- - - - - - - - - - - - - - - - - - -
On Fri, Jan 8, 2021 at 1:27 AM Sean Conner <sean at conman.org> wrote:
How should the client (or a URI/URL/IRI parser) deal with such links.IMO they should decode all characters allowed in that section of theURL. For example, a %2f wouldn't be decoded, because it would splitthe path segment. %61 would, because it decodes to "a", which isallowed and wouldn't change the meaning. The Chrome (Might actually beV8, idk) and Firefox URL parsers do this for HTTP(S), but not otherprotocols.I think this makes sense because it makes a single normalized form,and allows for files with special characters in their names. I'm notsure how servers would handle filenames with slashes in them, though.
- easrng