It was thus said that the Great Petite Abeille once stated: > > > > On Dec 27, 2020, at 01:26, Sean Conner <sean at conman.org> wrote: > > > > How do you preseve them? As the encoded "%2F"? Do you convert the > > encoded values to uppercase? Lowercase? Keep them the same? > > The hex code themselves? I tend to normalize them to uppercase. Tradition > or something. But perhaps we are talking about different things? Or? I meant: If I gave your URL parsers the string Research/A%2fB%20Testing/Results what would I, as a user, get back? Would I get a string back? An array of segments? An actual example would be be nice. > > Well, I do have one [1], although I'm not sure how "full-fledged" it is. > > Yes, but this only concerns itself with the content-type header. I mean > MIME multipart constructs. Ah. See, I haven't needed that much functionality yet (and I suspect I could use my email parsers for that if I really needed it). -spc [1] Missing footnote.
---
Previous in thread (107 of 109): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)
Next in thread (109 of 109): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)