URL-Encoded Form Data Body Regex for JavaScript
/^[a-zA-Z0-9%+\-_.~!$'()*,;:@/?]+(?:=[a-zA-Z0-9%+\-_.~!$'()*,;:@/?]*)?(?:&[a-zA-Z0-9%+\-_.~!$'()*,;:@/?]+(?:=[a-zA-Z0-9%+\-_.~!$'()*,;:@/?]*)?)*$/What this pattern does
This page provides a comprehensive, battle-tested regular expression for matching url-encoded form data body, ported and verified for JavaScript. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your JavaScript project — whether you're validating in an Express middleware, a Next.js API route, or a client-side form.
Javascript Implementation
// URL-Encoded Form Data Body
// ReDoS-safe | RegexVault — Web & Network > Misc
const urlencodedFormDataBodyRegex = /^[a-zA-Z0-9%+\-_.~!$'()*,;:@\/?]+(?:=[a-zA-Z0-9%+\-_.~!$'()*,;:@\/?]*)?(?:&[a-zA-Z0-9%+\-_.~!$'()*,;:@\/?]+(?:=[a-zA-Z0-9%+\-_.~!$'()*,;:@\/?]*)?)*$/;
function validateUrlencodedFormDataBody(input: string): boolean {
return urlencodedFormDataBodyRegex.test(input);
}
// Example
console.log(validateUrlencodedFormDataBody("key=value")); // trueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
key=value | =value |
foo=bar&baz=qux | &key=value |
q=hello+world&page=1 | key=val ue |
encoded=%2Fpath&flag | key==value |
a=1&b=2&c=3 | key=val& |
When to use this pattern
This pattern is drawn from the Web & Network > Misc category and carries a ReDoS-safe certification. That matters for JavaScript developers because especially critical in long-running Node.js event loops where a ReDoS vulnerability can block the entire process. 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
Always URL-decode values before processing. Be alert to double-encoding (%2520 = encoded %20) — normalize encoding depth before validation.
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=).
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