But what's the problem? Maybe you could provide an example of how your code is failing to deal with '/' properly. In the following example I decode your sample JSON, grab the key that looks like a regular expression, compile it as a regular expression, and use it to perform a match.

use strict;
use warnings;
use JSON;

use constant KEY   => 0;
use constant VALUE => 1;

my $json_string = <<'END_JSON';
{
  "regex" : {
    ".*/home/members/index.htm.*" : {
      "404" : {
        "reporting" : "1000",
        "paging" : "2000"
      }
    }
  }
}
END_JSON

my @test_strings  = qw( 
  web/home/members/index.htm?garbage=bye
  /home/memberzzzz/index.htm?garbage=bye
);

my $decoded_json = JSON->new->decode( $json_string );

# The regex is contained within a hash key.
my $regex_string = (%{$decoded_json->{regex}})[KEY]; 

my $regex        = qr/$regex_string/;

foreach my $test_string ( @test_strings ) {
  if( $test_string =~ m/$regex/ ) {
    print "Bingo! [$test_string] matches the pattern '$regex_string'\n
+";
  }
  else {
    print "Boo! [$test_string] doesn't match the pattern '$regex_strin
+g'\n";
  }
}

[download]

No special escaping of '/' here. The qr// operator is convenient.


Dave

In reply to Re^3: Regex in json: escaping forward slash by davido
in thread Regex in json: escaping forward slash by mhearse

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.