Extract URL parts only named capturing groups

Parses the text following a '#' and a space all the way up to the next return character. Additional #'s can be added for parsing of other type of headings!

Validates subdomain, root domain, and wild card domains

Case insensitive match the whole word betwween \bword\b

match: #aabbcc #abc (255,255,255) (255,255,255,255) 255,255,255 no match: #gggggg #ggg 256,256,256

Regular expression to check the email syntax validity. Certainly requires improvement, but it's a good basis to work from. Work with Java and JavaScript.

Crude CSV regex to split only by characters surrounded by non-whitespace characters. Ignore that it dosen't highlight all of the other commas in the editor. If you select the g regex flag it will properly show here, but not work in Java. Credit to @merosity (Merosity#0135) on Discord!

Matching for mikrotik ROS 7 Used in promtail and grafana

Aquivalent solution for golang's unsupported negative lookahead in re2 flavor of go's regex. This example provides a negative lookahead similar to (?!/api/) ignoring routes with the /api/ prefix at the start.

Regex to select PlantUML Block in Asciidoc documents

^(((\d{3}1-9]|\d{2}[1-9]\d|\d[1-9]\d{2}|[1-9]\d{3})(\/)(((0[13578]|1[02])(\/)(0[1-9]|[12]\d|3[01]))|((0[469]|11)(\/)(0[1-9]|[12]\d|30))|(02(\/)(0[1-9]|[1]\d|2[0-8]))))|(((\d{2})(0[48]|[2468|13579)|((048]|[2468|3579)00))(\/)02(\/)29))$ Match year/month/day, date format. E.g: 2021/08/25 [match] 2021/09/30 [match] 2018/02/28 [match] 2024/02/29 [match] 2023/02/29 [mismatch]

Regex expression for comparing decimal numbers with the usual comparison operators such as (greater than), >= (greater than or equal to), != (not equal to), == (equal to), ... The regex also allows filtering of data from e.g. a database, whereby the first value is not needed, e.g. [FIELD] < 100

Simple prefix matcher for validating URI Schemes according to [RFC2396, Section 3.1]( http://www.faqs.org/rfcs/rfc2396.html#3.5:~:text=well%20as%20%22http%22%29.-,scheme%20%20%20%20%20%20%20%20%3D%20alpha%20*%28%20alpha%20%7C%20digit%20%7C%20%22%2B%22%20%7C%20%22%2D%22%20%7C%20%22.%22%20%29,-Relative%20URI%20references) Go Playground: https://go.dev/play/p/vtYEugsNAfo

Analyze whether the torrent name is a Movie or TV Episode Inspired from https://regex101.com/library/yP4bY4 There is two versions, see differences at the bottom Groups: Title (of the Movie/of the TV Series) Season (if TV Episode) Episode (if TV Episode) Year (if Movie) Name (only in v1, should match the TV Episode title if present) Release name (PROPER, REPACK, LIMITED, etc..) Resolution (720p, 1080p, etc..) Quality (HDTV, BluRay, WebRip, etc..) Codec (Xvid, x265, x264, etc..) Audio coding (AAC, AC3, DTS, etc...) Team (torrent group/team) Extension (mkv, avi, mp4, etc...) Versions: v1, include the TV Episode title, and have all the groups in a single match, but will misinterpret the "name" and "team" groups if the expected pattern is not respected (see in the test strings/regex rules) v2, does not include "name" group but is more reliable, will ignore unexpected patterns.

A regex for validating decimal numbers in the European number format (in many parts of Europe at least, including Germany). A comma is used as a separator for the decimal number, a dot as a separator for thousand places.

Flagged / disallowed text expression used in cApStAn's build of OmegaT

Custom tags expression used in cApStAn's build of OmegaT

"^([\w_]+)(?:\{(*)\})?\s+([\d\\.e+-]+)(?:\s+(\d+))?$"gm

https://regex101.com/r/hIak43/1

W alpha/

Validation pattern to validate the minimum_should_mach value in opensearch and elasticsearch queries. For more information on the minimum_should_match field have a look here for opensearch or here for elasticsearch

Parse the typical connection string address like 123.123.123.123:123, supports the correct port and octet range

regex of challenge

Simple Regex to *validate * (no extraction!) an IPv4 Range which can be a comma separated mixture of IPv4 addresses IPv4 CIDRs IPv4 Ranges like 1.1.1.1-1.1.1.10 Examples : 192.168.1.1,255.255.255.255/32,10.10.10.10/24,0.0.0.0/24 192.168.1.1/32 192.168.1.1 192.168.1.1/32 192.168.1.1/12 192.168.1.1/24 192.168.1.1/24 192.168.1.1/0,192.168.1.1/0 10.0.0.0/24 172.16.0.1-172.16.0.255 192.168.1.1,10.0.0.1/24,172.16.0.1-172.16.0.10 64.33.232.212 64.33.232.210/24

This is made to validate an ISO 8601 input in a Terraform variable validation block: validation { condition = can(regex("^P(\\d+Y)?(\\d+M)?(\\d+D)?(T(\\d+H)?(\\d+M)?(\\d+S)?)?$", var.value)) error_message = "The value must be a valid ISO 8601 duration string representing time. (e.g. PT1M, PT1H30M, PT30S, etc.)" }

...

Addes a non-breaking space after any of the letters included in the [vozuskia] class.

Splits a Docker image string into the separate parts: image, tag, digest tag and digest are optional

Gets the ID of a YouTube Video from any link to it.

get prefecture from Japanese address

This validates AWS EventBridge scheduling expressions using the rate() and cron() formats. It may not catch all invalid expressions, but it should properly validate all valid expressions, as demonstrated in the unit tests. Please let me know if I missed any valid expressions. Originally attempted this using named capture groups and named back-references to reduce duplication. Unfortunately, named capture support is tricky, so they were all converted to duplicated non-capturing groups instead.

Parses an IANA Media Type value. Doesn't seem to capture repeating parameters, which is a bit of an edge case but valid I think - any suggestions on how to fix would be appreciated.

操作系统文件名称验证，参考了Windows，Linux，Mac

verificare indirizzo IPV6 (regole base)

This is for my plugin project

Kafka loki parser

Extract youtube video ID

This regex expression is useful for extracting only the text string from a value in a column that may contain values from individual rows with repeat strings tagged with a suffix. For example - Row 1: "Sales (#1)", Row 2: "Sales Match (#2)". From the shared examples, this regex will extract the text "Sales" and "Sales Match."

0x28C6A6DdF8fF8A47A90A69bfE75cd89904a14d71

This is still a working in progress Need to do Unit Tests and search for more use cases Match partial cases of 8601 such as: missing offset missing time only date and offset nano present or not (and being from 1 digit to 9 digits) Also properly captures the data by capturing only: year, month, date, hour, minute, second, nano and offset (be it 'Z' or '+02:00' or' +0200')

Extract any link or endpoint from 1- HTML page source 2- HTTP responses 3- JS files Feel free to contact me on Telegram https://t.me/c4ir0 if you: are interested in discussing this regex need assistance with any regex-related queries want to challenge me (I'm enthusiastic about this part)

htnle

why did I make this?

Dj dus er geen je een je aan je enige eerst een he we er

see https://stackoverflow.com/questions/76228402/regex-to-extract-n-where-n-is-digit

Testing Authelia subdomain / path rules. You can read more at the Authelia Docs By default, this regex101 page is shown a test for a generic API path domain: "some-sub.drpranavmishra.com" resources: "^/api([/?].*)?$" # API paths "^/healthz.*$" # Health check "^/\?[\S]{40,70}$" # PrivateBin policy: bypass`

Gist link for Java : https://gist.github.com/Gencturk-m/9962ce1e1dcf4dd9307062e34b023183 Aşağıdaki yapıdaki plakaları kabul eder: "01-81 X 9999", "01-81 X 99999" "01-81 XX 999", "01-81 XX 9999" "01-81 XXX 99" "01-81 XXX 999" **X: Türkçe'nin ÖÇŞİĞÜ hariç büyük harfleri. **Harfler ve sayılar arasında boşluk olmadan kabul eder. Boşluklu versiyonu gist linkinde var. **00, 000, 0000 ve 00000 ile bitenleri kabul etmez. **X: Turkish Capital Letters except ÖÇŞİĞÜ. **There is no white-space between letters and numbers. White-space version is in gist link. **Does not accept plates that ends with 00, 000, 0000 and 00000.

json value extract

Matches with the valid email addresses.

Replaces ^ with Math.pow function call. This assumes all braces have been combined first. If you need help with the combination, I got you—try this Python algorithm: def evaluate_braces(expr): """Recursively evaluate expressions within braces""" Check if expression contains braces if '(' in expr: Find the innermost set of braces left = expr.rfind('(') right = left + expr[left:].find(')') Evaluate the expression within the braces result = eval(expr[left+1:right]) Replace the expression within the braces with its result expr = expr[:left] + str(result) + expr[right+1:] Recursively evaluate any remaining expressions within braces expr = evaluate_braces(expr) Evaluate the final expression return expr expression = "31+((4+1)+27)2" result = evaluate_braces(expression) print(result) # Output: 2+2+3+4*8/2