Question 1

What does the HTTP/HTTPS URL regex pattern do?

Accepted Answer

Matches URLs with http or https protocol, domain with TLD, optional path segments, query string parameters, and fragment identifiers.

Question 2

How do I use the HTTP/HTTPS URL regex in JavaScript?

Accepted Answer

Use the pattern /https?://[\w.-]+(?:\.[a-zA-Z]{2,})(?:[/\w.-]*)*(?:\?[\w=&.-]*)?(?:#[\w-]*)?/gi with the String.match() or String.matchAll() method. For example: const matches = text.match(/https?://[\w.-]+(?:\.[a-zA-Z]{2,})(?:[/\w.-]*)*(?:\?[\w=&.-]*)?(?:#[\w-]*)?/gi);

Question 3

What regex flags does this pattern use?

Accepted Answer

This pattern uses the global, case-insensitive flags (gi). The global flag finds all matches in the input, not just the first. The case-insensitive flag matches regardless of letter casing.

Question 4

Which programming languages support this regex?

Accepted Answer

Fully supported in JS, PYTHON, JAVA, PHP, GO, RUBY, CSHARP

Question 5

What strings does this regex match?

Accepted Answer

This pattern matches strings like: https://example.com, http://sub.domain.co.uk/path?q=1#top, https://api.example.com/v2/users. It does not match strings like: ftp://files.com, example.com, not-a-url.

Question 6

When should I use the HTTP/HTTPS URL regex?

Accepted Answer

Use this pattern to extract or validate HTTP/HTTPS URLs from plain text such as user comments, log files, or documents. For strict URL parsing, use the built-in URL constructor (JavaScript) or urllib.parse (Python) instead. This pattern covers common URL formats but does not handle internationalized domain names (IDN) or URLs with encoded special characters.

Question 7

What are common mistakes with the HTTP/HTTPS URL regex?

Accepted Answer

A common mistake is: Forgetting to escape the dot before the TLD, e.g., [\w.-]+.[a-zA-Z]{2,}. Instead, use [\w.-]+\.[a-zA-Z]{2,} because An unescaped dot matches any character, causing the pattern to match strings like https://example_com as valid URLs.. A common mistake is: Using greedy .* for the path instead of a restricted character class. Instead, use (?:[/\w.-]*)* because A greedy .* can match far beyond the URL boundary and may cause catastrophic backtracking on long inputs. Use a character class that only allows valid URL path characters.. A common mistake is: Not including the query string and fragment portions. Instead, use (?:\?[\w=&.-]*)?(?:#[\w-]*)? because URLs frequently include query parameters (?key=value) and fragment identifiers (#section). Without these groups, valid URLs like https://example.com/search?q=test are only partially matched.

Question 8

How does the HTTP/HTTPS URL regex work step by step?

Accepted Answer

`https?` — Match 'http' followed by an optional 's' — covers both HTTP and HTTPS protocols. `://` — Match the literal protocol separator '://'. `[\w.-]+` — Match one or more word characters, dots, or hyphens — the domain and any subdomains (e.g., 'api.example'). `(?:\.[a-zA-Z]{2,})` — Match a dot followed by two or more letters — the top-level domain (.com, .org, .co.uk). `(?:[/\w.-]*)*` — Match zero or more path segments containing slashes, word characters, dots, or hyphens. `(?:\?[\w=&.-]*)?` — Optionally match a query string starting with ? containing key=value pairs separated by &. `(?:#[\w-]*)?` — Optionally match a fragment identifier starting with # (e.g., #section-1)

Token	Explanation
`https?`	Match 'http' followed by an optional 's' — covers both HTTP and HTTPS protocols
`://`	Match the literal protocol separator '://'
`[\w.-]+`	Match one or more word characters, dots, or hyphens — the domain and any subdomains (e.g., 'api.example')
`(?:\.[a-zA-Z]{2,})`	Match a dot followed by two or more letters — the top-level domain (.com, .org, .co.uk)
`(?:[/\w.-])`	Match zero or more path segments containing slashes, word characters, dots, or hyphens
`(?:\?[\w=&.-]*)?`	Optionally match a query string starting with ? containing key=value pairs separated by &
`(?:#[\w-]*)?`	Optionally match a fragment identifier starting with # (e.g., #section-1)

Language	Support
JS	Full support
PYTHON	Full support
JAVA	Full support
PHP	Full support
GO	Full support
RUBY	Full support
CSHARP	Full support

HTTP/HTTPS URL

Pattern

Try It

Explanation

When to Use

Step-by-Step Breakdown

Common Mistakes

Test Strings

Matching

Non-matching

Language Compatibility

Code Snippets

Common Variations

HTTPS only

Related Patterns

URL with Any Protocol

Domain Name

Learn the Concepts