Do we also want:
3. Has an unambiguous decoding.
Replacing '/' with '#%$' means I don't know if the user actually supplied
'#%$' or '/'. But using something like percent-encoding would have property
3.
On Fri, Jul 6, 2018 at 10:25 AM, Greg Mann wrote:
> Thanks for the reply Ben!
>
> Yea I
Thanks for the reply Ben!
Yea I suspect the lack of normalization there was not intentional, and it
means that you can no longer reliably split on '/' unless you apply some
external controls to user input. Yep, this is bad :)
One thing we should consider when normalizing metadata embedded in
2 matches
Mail list logo
