Why Treating "null" as Empty Causes Silent Registration Bugs

Recently a humorous post about a user choosing the name "null" sparked a deeper look into a recurring bug that many developers encounter during user registration.

The core issue is that the string "null" is not the Java null keyword; it is a regular, non‑empty string surrounded by quotes, so treating it as an empty value introduces a bug.

Typical problematic JSON payloads look like this:

{
  "username": "null",
  "password": "123456"
}

A common backend validation snippet might be:

if (user.getUsername() == null) {
    throw new IllegalArgumentException("用户名不能为空");
}

Because the incoming value is the literal string "null", the condition never triggers, allowing the account to be created as if it were valid. The user then appears in the system, causing confusion when sending emails, assigning permissions, or checking for duplicate usernames.

To avoid this "ancestor" pitfall, developers should explicitly check for the string "null" (and other placeholder values), trim whitespace, and enforce proper null handling in both front‑end and back‑end validation layers.