Networkingflags: g

Generic Connection String (URL Form)

Parse generic URL-form connection strings: `protocol://[user[:pass]@]host[:port][/database]`.

Try it in RegexPro →

Available in

JSSupported

JavaScript / ECMAScript

Browser-native RegExp. Default if you don't pick.

PYSupported

Python (re)

CPython stdlib `re`. Unicode-aware `\w` and `\d` by default.

GOSupported

Go (RE2)

Linear-time matching. No backreferences or lookarounds.

Pattern

regexengine-agnostic
([a-zA-Z][\w+\-.]*):\/\/(?:([^:@\s]+)(?::([^@\s]*))?@)?([^:\/\s]+)(?::(\d+))?(?:\/([^?\s]*))?   (flags: g)

Raw source: ([a-zA-Z][\w+\-.]*):\/\/(?:([^:@\s]+)(?::([^@\s]*))?@)?([^:\/\s]+)(?::(\d+))?(?:\/([^?\s]*))?

How it works

Group 1 captures the scheme (postgres, mysql, redis, mongodb, kafka, etc.). The optional auth section captures user and optional password. Group 4 is the host. Optional port and path captures follow. This is a working starting point for parsing many SaaS connection strings; for production use a real URL parser.

Examples

Input

postgres://admin:s3cret@db.example.com:5432/main

Matches

  • postgres://admin:s3cret@db.example.com:5432/main

Input

kafka://broker.internal:9092

Matches

  • kafka://broker.internal:9092

Input

no connection here

No match

—

Common use cases

  • •Config file linting and secret detection
  • •Migration scripts that re-write connection details
  • •Observability — surfacing target hosts from logs
  • •Feature gating by environment (parse host suffix)
←PreviousKeep-a-Changelog Entry Header
All patterns
NextRedis Connection URL→