Hi, Looking at these CVEs, they apply to the following versions of libxml2: - CVE-2016-4658: "

Hi, Thanks for asking this question. Ruby 2.4 is quite old, so you may be in for a bit of tough time.

Sorry you're having a problem. Please open an "installation difficulties" issue and

The result you want is not valid XML, so Nokogiri will not do that for you. The correct way that your

Hi Keith, Great question. In theory libxml2 supports multiple threads, but only one-thread-per-

Yes! You can append to an existing style. Node#[] is documented here: https://nokogiri.org/rdoc/

Nokogiri v1.13.6 has been released with a security update for CRuby users. The release notes are

Nokogiri v1.13.5 has been released with a security update for CRuby users. The changelog entry is

200000 line XML and the data of interest looks like the following (extraneous info removed). There

Nokogiri v1.13.0 has been released! This is a feature update focused on Ruby 3.1 native (precompiled)

Nokogiri v1.12.5 was released on 2021-09-27 which contains a fix for CVE-2021-41098, fully described

Hi, This error message is sometimes output if you've upgraded or changed your Ruby version but

Nokogiri v1.12.0 has been released! This is a feature update focused on HTML5 DOM parser support. ---

Nokogiri v1.11.4 was released on 2021-05-14, which contains an updated version of libxml2 that

Thanks Mike, I'll do that. I did the workaround for now and after builder was done with it,

Nokogiri v1.11.0 was released on 2021-01-03, which contains a fix for CVE-2020-26247, fully described

Nokogiri version 1.11.0 has been released. This is a significant release containing installation

Thanks for closing the loop here! I'm glad you were able to figure it out. Cheers! -mike On Mon,

Thank you so much! Just what I needed! On Thu, Nov 5, 2020 at 5:40 AM Mike Dalessio <mike.dalessio

To add a bit more context around what Mike stated. Right now you have an invalid xpath. Here is how

Hey Jack, I'm happy to hear you were able to make this work! On Thu, Oct 8, 2020 at 3:59 PM Jack

FWIW, the problem goes away when I “bundle install” instead of “gem install”. On Sep 29, 2020, at 5:

An update : As part of the upgrade process, I tried upgrading to Ruby 2.3.8. Here surprisingly

Out put of ldd attached in previous email indicates missing libruby.so.2.7 so I recompiled ruby 2.7.0

Hi, I'm running a Rails 6.0.2.2 app using the default Rails Puma web server on my local

Hi all, Please see https://github.com/sparklemotion/nokogiri/issues/2075 for more context. Nokogiri

Just as an aside, this question and use case are really well-suited to be an example in the Nokogiri

Thank you, Mike, for your help. After a few hours of trying to resolve this, what finally worked was

Hi Martin, Thanks for asking this question. Yes, you're describing the same issue as #572. A

John Shahid wrote on 2020-07-15 08:05: > I think the location is coming from the XML document that