Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the URI-Find CPAN distribution.

Report information
The Basics
Id: 44557
Status: rejected
Priority: 0/
Queue: URI-Find
People
Owner: Nobody in particular
Requestors: nine [...] detonation.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 20090316
Fixed in: (no value)

History Show all quoted text
  Wed Mar 25 09:28:51 2009 nine [...] detonation.org - Ticket created
Subject: URI::Find finds unwanted URIs in DOCTYPEs
As of version 20090316, URI::Find finds the URI in a DOCTYPE like: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> and also in an xmlns like: <html xmlns="http://www.w3.org/1999/xhtml/"> this has the unwanted consequence of Catalyst::Plugin::Session::State::URI completely destroying the DOCTYPE directive as in: <!DOCTYPEhtmlPUBLIC%22-//W3C//DTDXHTML1.0Strict//EN%22%22http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd/-/a0888fbf7d606f31b48ea971713780e3a769b110"> <htmlxmlns=%22http://www.w3.org/1999/xhtml/-/a0888fbf7d606f31b48ea971713780e3a769b110"> While one could argue, that URI::Find just does it's job and got better at it, this is creating real world problems. Also one could argue that in these two cases, the URI is no URI as such, but instead a globally uniquie identifier, using URI syntax to ensure the uniqueness. And indeed, the W3C recommendation explains them as such.
  Thu Feb 11 06:59:53 2010 mschwern [...] cpan.org - Correspondence added
On Wed Mar 25 09:28:51 2009, NINE wrote: Show quoted text
> As of version 20090316, URI::Find finds the URI in a DOCTYPE like: > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 > Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > and also in an xmlns like: > <html xmlns="http://www.w3.org/1999/xhtml/">
... Show quoted text
> While one could argue, that URI::Find just does it's job and got > better > at it, this is creating real world problems. Also one could argue that > in these two cases, the URI is no URI as such, but instead a globally > uniquie identifier, using URI syntax to ensure the uniqueness. And > indeed, the W3C recommendation explains them as such.
A globally unique identifier... identifying a resource? Universally? Sorry, I'm going to have to reject this one. URI::Find is doing its job, it finds URIs and that most definitely is a URI. Its up to you to decide if they're of interest and what you do with them. This may have been exasperated by the bug where URI::Find was mangling URIs inside brackets. Why are you running URI::Find over HTML?
  Thu Feb 11 06:59:54 2010 The RT System itself - Status changed from 'new' to 'open'
  Thu Feb 11 06:59:55 2010 mschwern [...] cpan.org - Status changed from 'open' to 'rejected'