Bug #57032 for URI-Find: Doesn't find a valid URI following a "\w.http", e.g. "club...http://bit.ly/9QfKVL"

Thu Apr 29 05:15:33 2010 avar [...] cpan.org - Ticket created

Subject:

Doesn't find a valid URI following a "\w.http", e.g. "club...http://bit.ly/9QfKVL"

While working on Bot::Twatterhose I noticed that URI::Find fails on ~0.5% of URLs posted on Twitter (16/2583 in my tests from /public_timeline). This is because it doesn't grok $schema://[..] directly following e.g. "foo...", i.e. "foo...http://x.org". Here's a real world example of a Twitter user expressing concern over what he perceives to be an effeminate dance act: #letsbeclear this dance is super gay & I bet not ever see a n*gga doin it in the club...http://bit.ly/9QfKVL Another example: The technology of magnetic energy has become so powerful an entire house can...http://bit.ly/8yEdeb Due to this serious bug I've been missing out on the latest dance moves, and I've apparently been paying too much for my energy.

Tue May 04 13:29:11 2010 mschwern [...] cpan.org - Correspondence added

On Thu Apr 29 05:15:33 2010, AVAR wrote: Show quoted text

> While working on Bot::Twatterhose I noticed that URI::Find fails on > ~0.5% of URLs posted on Twitter (16/2583 in my tests from > /public_timeline). This is because it doesn't grok $schema://[..] > directly following e.g. "foo...", i.e. "foo...http://x.org".

The issue is that "foo...http" is a validly formatted scheme, so URI::Find picks up the whole of "foo...http://x.org" but then rejects it because its not a recognized scheme. Since nobody actually uses non-alphanumerics in schemes, I'll just remove them from the regex. The fix will be in the next release shortly.

Tue May 04 13:29:14 2010 The RT System itself - Status changed from 'new' to 'open'

Tue May 04 13:29:36 2010 mschwern [...] cpan.org - Status changed from 'open' to 'resolved'

Bug #57032 for URI-Find: Doesn't find a valid URI following a "\w.http", e.g. "club...http://bit.ly/9QfKVL"

Preferred bug tracker