REGEXVAULTv2.0
Web & Network/URL
Verified Safe

URL Percent-Encoding Validation Regex for Java

/^(?:[a-zA-Z0-9\-._~!$&'()*+,;=:@/?#\[\]]|%[0-9a-fA-F]{2})*$/

What this pattern does

This page provides a well-structured, multi-part regular expression for matching url percent-encoding validation, 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

Java
// URL Percent-Encoding Validation
// ReDoS-safe | RegexVault — Web & Network > URL

import java.util.regex.Pattern;

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

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

    // Example
    public static void main(String[] args) {
        System.out.println(validate("/path/to%20resource")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
/path/to%20resource/path%2Gfoo
query=hello%20world/path%2
%2F%41%42%43/path%
/valid%2Fpath/path%ZZbad
no-encoding-needed/path% 20space

When to use this pattern

This pattern is drawn from the Web & Network > URL category and carries a ReDoS-safe certification. 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

A % not followed by two hex digits is malformed and must be rejected or escaped as %25. Many parsers silently corrupt malformed percent sequences.

Technical Notes

This pattern validates encoding structure, not meaning. %2F is technically valid encoding but may have semantic implications (encoded forward slash vs. path separator) that require application-level handling.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern