rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: "Chris St. John" <chris@stjohnstudios.com>
To: rack-devel@googlegroups.com, nunemaker@gmail.com
Subject: Re: Rack Uses Regex That Occasionally Causes REE to Hang
Date: Tue, 12 Jul 2011 20:42:11 -0400	[thread overview]
Message-ID: <CAOYouXXQN3NnBqu-e=rhxEFxUEx9tssD7Hc16CGKjx_bdxbfAA@mail.gmail.com> (raw)
In-Reply-To: <6448086.93.1310513292626.JavaMail.geo-discussion-forums@yqyy3>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

I tested the regex with 1.8.7, 1.9.2, and JRuby 1.6.1.  All seem to hang and
show the same behavior you see with REE.  Seems to be an issue with Ruby's
regex engine on all distros.  FWIW, out of curiosity I ran the same regex in
Perl, which handled it quickly and correctly.

Chris

On Tue, Jul 12, 2011 at 7:28 PM, John Nunemaker <nunemaker@gmail.com> wrote:

> Posted the REE issue to the REE google group as well:
> https://groups.google.com/forum/#!topic/emm-ruby/EBkMfFpk40A
>
> The regex used on line 61 in rack/backports/uri/common.rb<https://github.com/rack/rack/blob/1.3.0/lib/rack/backports/uri/common.rb#L61>causes REE to hang for certain strings. I only know because it happened in
> production over and over the past week and today, with help, I was finally
> able to track it down.
>
> Not sure if this is really an issue with Rack or just with REE, but it will
> affect anyone using Rack 1.3.0 and REE so I thought I would mention it here
> as well.
>

[-- Attachment #2: Type: text/html, Size: 1414 bytes --]

      reply	other threads:[~2011-07-13  0:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 23:28 Rack Uses Regex That Occasionally Causes REE to Hang John Nunemaker
2011-07-13  0:42 ` Chris St. John [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOYouXXQN3NnBqu-e=rhxEFxUEx9tssD7Hc16CGKjx_bdxbfAA@mail.gmail.com' \
    --to=rack-devel@googlegroups.com \
    --cc=nunemaker@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).