ow.

• Arbitrary remote code execution bug. (e.g. <a href=";rm[tab]-rf[tab]/">)
  ?, & and ; are very common characters in URLs which are also shell metacharacters.
• Useless overhead due to recursion.
  Breadth-first usually works better anyway.
• Useless overhead from using curl instead of LWP.
• Relative links aren't handled at all.
• Tries to extract links from non-HTML documents.
• Doesn't extract all links that could reference HTML docs.
  It's baffled by frames, for example.
• No throttling or robot niceties.
• No check is done to see if a page has already been visited. (Update)
• No constraints limiting the spidering to a domain or URL path. (Update)
• It checks the depth after extracting the links and spawning numerous instances of perl while it could do so before. (Update)

Naïve means simple, not bad.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.