I’d bet it’s less simple input sanitizing and more 2 mistakes made separately because they don’t know any better.
The input field converting everything to a string indiscriminately
Because they did 1, converting everything back to the assumed type
If the front end Dev makes the first mistake, null would be sent in the body as “null”. Then on the backend, somebody might even be binding the variables correctly, but before hand realizing they have to deal with the market and rather than just have a conversation undoes it in their own code.
Who the hell writes
if 'null'? If it’s a thing, what language would interpret a string like that?Fucking JavaScript
No it doesn’t?
> Boolean(null) false > Boolean('null') true > null == 'null' falseSrsly?
Javascript is fun. The video takes a few jabs at ruby and then gives a glimpse into the insanity that is Javascript.
More of this please
!![] + !![] == 2I’d bet it’s less simple input sanitizing and more 2 mistakes made separately because they don’t know any better.
If the front end Dev makes the first mistake, null would be sent in the body as “null”. Then on the backend, somebody might even be binding the variables correctly, but before hand realizing they have to deal with the market and rather than just have a conversation undoes it in their own code.
It’s fine in PHP, so that catches most server backends.
Ruby as well, it even raises a warning about the string where a bool should be!
Python handles it just fine, as well.
Rust doesn’t allow it, depending on the backend framework and server software this might give issues.
The same goes for C# .NET
So depending on how this is handled a C# or Rust backend might cause the name not to be stored, but then I’d expect nothing to be stored… :/