Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 30-Oct-2024 03:40:29 JST Haelwenn /элвэн/ :triskell:

   • Tulip ?️‍⚧️
   @domi @easrng Wouldn't be surprised of it being super-legacy from pre-RFC1738 (December 1994).
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 30-Oct-2024 03:44:28 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Tulip ?️‍⚧️
     @domi @easrng Also always kind of funny to me how HTTP/1.0 first got in IETF RFCs via RFC1945 (May 1996).
   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Wednesday, 30-Oct-2024 10:56:49 JST Erin 💽✨

     in reply to

     • Tulip ?️‍⚧️
     • Erin 💽✨
     @lanodan @domi @easrng anyway the URL generic syntax specs a bunch of extra reserved characters so the person *defining* a given URL or URL scheme can use them as delimiters, use their encoded form to escape values that contain said delimiters, and not have generic URL parsers mangle things
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Wednesday, 30-Oct-2024 10:56:51 JST Erin 💽✨

     in reply to

     • Tulip ?️‍⚧️

     @lanodan @domi @easrng prospero:// URLs from 1738 use ;parameters

     also RFC2396 requires escaping it in path segments b/c its used for path params:

     path = [ abs_path | opaque_part ] path_segments = segment *( "/" segment ) segment = *pchar *( ";" param ) param = *pchar pchar = unreserved | escaped | ":" | "@" | "&" | "=" | "+" | "$" | ","

     An example of a URI scheme using params is IMAP: imap://joe@example.com/INBOX/;uid=20/;section=1.2