URL-Encoded Form Data Body Regex for Java

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching url-encoded form data body, ported and verified for Java. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

// URL-Encoded Form Data Body
// ReDoS-checked | RegexVault — Web & Network > Misc

import java.util.regex.Pattern;

public class UrlencodedFormDataBodyValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^[a-zA-Z0-9%+\\-_.~!$\'()*,;:@/?]+(?:=[a-zA-Z0-9%+\\-_.~!$\'()*,;:@/?]*)?(?:&[a-zA-Z0-9%+\\-_.~!$\'()*,;:@/?]+(?:=[a-zA-Z0-9%+\\-_.~!$\'()*,;:@/?]*)?)*$");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("key=value")); // true
    }
}

Test Cases

When to use this pattern

This pattern is drawn from the Web & Network > Misc category and has been checked for ReDoS risk. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Technical Notes

Spaces are encoded as + (form encoding) or %20 (percent encoding). Both are valid. The pattern accepts key-only parameters (no = sign) and empty values (key=).