Nokogiri-使用XML，而不是HTML-Nokogiri-WorkswithXML,notsomuchwithHTML

5  

To debug this sort of problem we need more information from you. Since you're not giving a working URL, and because we know that Nokogiri works fine for this sort of problem, the debugging falls on you.

要调试此类问题,我们需要您提供更多信息。由于您没有提供有效的URL,并且因为我们知道Nokogiri可以解决这类问题,所以调试工作就在您身上。

Here's what I would do to test:

这是我要做的测试:

In IRB:

1. Do you get output when you do: open('http://whateverURLyouarehiding.com').read

当你这样做时,你得到输出:open('http://whateverURLyouarehiding.com')。read

2. If that returns a valid document, what do you get when you wrap the previous open statement in Nokogiri::HTML(...). That needs to preserve the .read in the previous line too, so Nokogiri is receiving the body of the page, NOT an IO stream.

如果返回一个有效的文档,当你在Nokogiri :: HTML(...)中包装上一个open语句时会得到什么。这也需要保留前一行中的.read,因此Nokogiri正在接收页面的主体,而不是IO流。

3. Try #2 above, but remove the .read. That will tell if there's a problem with Nokogiri reading an IO stream, though I seriously doubt it has a problem since I use it all the time. At that point I'd suspect a problem on your system.

尝试上面的#2,但删除.read。这将告诉Nokogiri读取IO流是否存在问题,但我严重怀疑它是否存在问题,因为我一直使用它。那时我怀疑你的系统有问题。

4. If you're getting a document in #2 and #3, then the problem could be in your accessor; I suspect what you're looking for doesn't exist.

如果您在#2和#3中收到文档,则问题可能出在您的访问者身上;我怀疑你所寻找的东西是不存在的。

5. If it does exist, then check the value of doc.errors after Nokogiri parses the document. It could be finding errors in the document, and, if so, they'll be captured there.

如果确实存在,则在Nokogiri解析文档后检查doc.errors的值。它可能是在文档中发现错误,如果是这样,它们将被捕获到那里。