When I'm having trouble with a regex, I try to use as many different correct variations as I can, and see if any of them work. This helps me to rule out bad escaping and the like as possible causes.

You might try the following:

/\?id\+(\d+)/
/.id.(\d+)/
/(/d{7})/
/.id.([^ ]+)/

[download]

and whatever else you can think of. Try reducing it to the simplest possible regex you can think of that will work, even if you know it won't work in the general case, or even if it isn't as robust as you want it to be.

If not of this helps, it's time to run the debugger on your code and make sure the string is getting read in as you think it should be.

Good Luck,
Mark

In reply to Re: Logfile parsing (Moved from Q&A) by young perlhopper
in thread Logfile parsing (Moved from Q&A) by Russ

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.