'Just today, Azure's support system can't handle (among many things) the outlandish characters of "<" or ">".' My favorite way of breaking things is to go the

'Just today, Azure's support system can't handle (among many things) the outlandish characters of "<" or ">".' My favorite way of breaking things is to go the other way... oh, you won't allow < or >? Well, how about ＜ and ＞? That's ok then? Great! One I've done several times is encounter a field that "can't be left empty", and is smart enough to filter out the ASCII whitespace before the check... but isn't smart enough to filter out the Unicode zero-width space. "A computer wizard never says too much or too little, he says precisely what he means to."