The article looks very thorough and detailed from what I've seen. The TLDR version (for the regex part. They give a lot of context information as well) would be this sentence:

what's important is any "real-world" expression (like the complex ones in our WAF rules) that ask the engine to "match anything followed by anything" can lead to catastrophic backtracking.
Basically /.*.*=/ is bad because the first .* will jump to the end of the string, and move back one character at a time, only for the second .* to take that character and start the whole process all over again before the engines gets a chance to check if the character is =.

I'm kind of surprised that the optimizer wouldn't remove such an obvious problem though. Maybe it's the non capturing group which prevents the two identical nodes from being merged. Or maybe their version of perl is too old and newer ones would have optimized that away correctly.

They don't mention it but I think the tool they used to turn the regexes into graphs is debuggex.


In reply to Re: Cloudflare uses Regexp::Debugger in explaining the outage by Eily
in thread Cloudflare uses Regexp::Debugger in explaining the outage by reisinge

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.