|
|
|
|
|
by RicoElectrico
1391 days ago
|
|
Bad design, this seems to be part of many legacy systems.
People tended to make bespoke textual formats, instead of, how we do now, using properly escaped serialization like JSON.
And because they couldn't bother making a robust parser with escaping, they went the lazy route of just disallowing characters with special meaning. |
|
When they forbid backslashes and quotes, it's even better: someone didn't know how to use query parameters or escape database values. It's a sign that their software is as secure as a "watch out for the dog" sign.