URL Protocol-Relative Regex for Java

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching url protocol-relative, 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 Protocol-Relative
// ReDoS-checked | RegexVault — Web & Network > URL

import java.util.regex.Pattern;

public class UrlProtocolrelativeValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^//(?:[a-zA-Z0-9](?:[a-zA-Z0-9\\-]{0,61}[a-zA-Z0-9])?\\.)+[a-zA-Z]{2,63}(?::(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3}))?(?:/[^\\s]*)?$");

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

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

Test Cases

When to use this pattern

This pattern is drawn from the Web & Network > URL 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

Protocol-relative URLs are deprecated in modern development. Prefer explicit https:// to avoid downgrade attacks when embedded in mixed-content pages.