Skip Menu |

This queue is for tickets about the HTML-Parser CPAN distribution.

Report information
The Basics
Id: 80524
Status: resolved
Priority: 0/
Queue: HTML-Parser
People
Owner: Nobody in particular
Requestors: haarg [...] haarg.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Wed Oct 31 10:47:50 2012 haarg [...] haarg.org - Ticket created
Subject: <meta> parsing registers invalid HTTP headers
<meta> tags can have name attributes with colons in them, and this is perfectly valid. But HTML::HeadParser then tries to register these as X-Meta-<name> headers using HTTP::Headers. Newer versions of HTTP::Headers (since 6.05) have stricter checks for headers, and will refuse them if they contain colons. I would think that HTML::HeadParser should either skip trying to add headers like this, or further reformat the name attribute before trying to use it in an HTTP header name.
  Wed Feb 06 17:31:59 2013 MARKSTOS [...] cpan.org - Correspondence added
I second this. This is currently an issue for anyone running this tool against a website home page that includes that includes the Pinterest domain verify code on their front page, since their meta tag name is "p:domain_verify". After upgrading LWP, my related code started failing. Here's the Pinterest docs for confirmation: https://help.pinterest.com/entries/22488487
  Wed Feb 06 17:32:00 2013 The RT System itself - Status changed from 'new' to 'open'
  Wed Feb 06 17:46:13 2013 MARKSTOS [...] cpan.org - Correspondence added
One solution would be to limit the <meta> tag parsing to the http_equiv headers. It seems then that the set of valid characters should be the same. Another solution would be to translate any characters in the meta tag that aren't valid in an HTTP header into something that is valid an HTTP header. For example, translate all such characters into dashes.
  Sat Mar 02 02:09:07 2013 haarg [...] haarg.org - Correspondence added
Even if there are invalid characters in an http_equiv header, it shouldn't cause parsing the document to fail. I think the two options are transforming the headers to a format that will be accepted, or just not registering such headers and continuing with parsing.
  Wed May 08 14:16:35 2013 jeremy.mates [...] gmail.com - Correspondence added
Yeah, dropbox downloads fail due to Twitter meta tags during the HTTP redirects to the download file: ... START[meta] 4.24 KB received Illegal field name 'X-Meta-Twitter:card' at /home/jmates/perl-5.16.3/lib/site_perl/5.16.3/OpenBSD.amd64-openbsd/HTML/HeadParser.pm line 207. Transfer aborted. Delete ...? [n]
  Wed May 08 18:15:03 2013 GAAS [...] cpan.org - Correspondence added
Fixed by https://github.com/gisle/html-parser/commit/a8f82837f7d1aae1aca24250b13814fef062ea33
  Wed May 08 18:15:04 2013 GAAS [...] cpan.org - Status changed from 'open' to 'resolved'