Regular Expressions 101

Community Library

23

Get path from any text

Created·2023-01-31 14:38
Updated·2023-07-23 20:17
Type·Match
Flavor·PCRE2 (PHP)
Recommended·
Get path (windows style) from any type of text (error message, e-mail corps ...), quoted or not. THIS IS THE SINGLE LINE VERSION ! If you want understand how it work or edit it, go https://regex101.com/r/7o2fyy Relative path are not supported The goal is to catch what "Look like" a path. See the limitations UNC path and prefix path like //./], [//?/] or [//./UNC/] are allowed some url path like [file:///C:/] or [file://] are allowed Catch path quoted with ["] and [']. But these quotes are include with the catch Quoted path is not concerned by limitations Limitations : (only unquoted path) [dot] and [space] is allowed, but not in a row [dot+space] or [space+dot at end of file name isn't catched INSIDE A NAME FILE (or last directory if it is a path to a directory) : [comma] is not supported (it stop the catch) after a first [dot], any [space] stop the catch after a [space], catch is stoped if next character is not a [letter], [digit] or [-] so, double [space] stop the catch Compatibility compatible PCRE, PCRE2 AutoHotkey : don't forget to escape "%" in "`%" /!\ Powershell and .Net /!\\ : this regex need some modification to be interpreted by powershell. You have to replace each (?&CapturGroupName) by \k. Use this powershell code to do this replacement : ` $powershellRegex = @' [Put here the regex to replace (?&CapturGroupName) with \k] '@ -replace '\(\?&(\w+)\)', '\k' ` This example code must return : [Put here the regex to replace \k with \k]
Submitted by nitrateag

Community Library Entry

0

Regular ExpressionOpen Workspace

/
^\[(?P<thread_name>\w+\-\d+)\]\s\d\d\d\d\-\d\d\-\d\d\s\d\d:\d\d:\d\d\s\[(?P<request_id>[^,]+),(?P<global_partner_code>[^,]+),(?P<plf_code>[^,]+),(?P<request_type>[^,]+),(?P<product_type>[^,]+),\d\d\-\d\d\-\d\d\d\d\s\d\d:\d\d:\d\d,(?P<server_name>[^,]+),(?P<check_in_date>[^ ]+)\s00:00:00,(?P<check_out_date>[^ ]+)\s00:00:00,(?P<requested_currency_code>[^,]+),(?P<requested_language_code>[^,]+),(?P<error_code>[^,]+),(?P<error_desc>[^,]+),(?P<gds_processing_time>\d+),(?P<total_processing_time>\d+),(?P<pre_gds_processing_time>\d+),(?P<post_gds_processing_time>\d+),(?P<post_processing_time>\d+),(?P<response_time>\d+),(?P<property_count>\d+),(?P<opaque_rate_request_count>\d+),(?P<merchant_rate_request_count>\d+),(?P<agency_rate_request_count>\d+),(?P<cached_rate_request_count>\d+),(?P<avail_request_count>\d+),(?P<rule_request_count>\d+),(?P<on_time_request_count>\d+),(?P<late_request_count>\d+),(?P<timeout_request_count>\d+),(?P<cache_read_time>\d+),(?P<cache_update_time>\d+),(?P<business_processing_time>\d+)\]
/

Description
Created·2016-06-07 13:48
Type·Match
Flavor·PCRE (Legacy)

For parsing the events from the RHSE searchstats log file

Submitted by Will
Open Workspace