5 ms·
Some of these systems which broke were almost certainly SQL injectable.
by loosescrews 7y ago
Some of these systems which broke were almost certainly SQL injectable.
- Piskvorrr 7y agoThe number of systems failing the "L'Oréal test" is staggering. (This one tests multiple assumptions: nonalphabetic names, nonascii names, capitalization. We have encountered a particularly unexpected name+address a long time ago, and the name kinda stuck ;))
- rovr138 7y agoAnd as someone with an accent on a letter of my name, what I find amazing of your example is that the apostrophe and é are part of ascii. No technical limitation on the computer if it supports ascii. It’s bad programming and assumptions.
- Kwpolska 7y agoé is not in ASCII. No accented leters are. You might be thinking of ISO-8859-1, or Windows-1252, which Windows misnames as "ANSI". But not all legacy/broken systems use these, they might be thinking in a different legacy encoding, which lacks an é.
- bmn__ 7y agoKwpolska, your account is shadowbanned, most posts from you are not displayed, although they are overwhelmingly useful/factually correct. I am unable to directly reply to your post, so need to go up one level and hope you see this post. (HN readers, if you don't understand what's going on, then enable "showdead" in your profiles.)
- Piskvorrr 7y agoApostrophe is within ASCII, but breaks sites that a) are prone to SQL injection and/or b) are prone to XSS, generally anything where it can be a control character. "é" is not in ASCII, you're thinking of some "extended ASCII" variant, such as Latin-n (where n goes from 1 to 12). Those are insidious, as your "of course é is in ASCII" becomes "of course ř is in ASCII", or something similar. Finding the original encoding then requires out-of-band signalling, or guessing (heuristics ;)). The technical limitations checked here are in bespoke code, not in the OS.