Preparing for netcurl 6.1.5

We’ve been holding on netcurl 6.1.5 for a while now, since the package has been a bit too small to be considered release worthy. However, the last days changed this and two bigger features has now been fixed: SoapClient timeouts and the ability to disable SSL certificate verification (which has been planned for long now).

SSL Verification becomes configurable

The verification issues is added as part to the fact that requests to self signed sites sometimes is necessary and normally netcurl security is set to never allow self signed or invalid SSL certificates. This release also contains a fix that makes the streamwrapper handle errors better, since we need to be able to catch SSL request exceptions.

SoapClient Timeouts

The SoapClient timeout handler has just recently become a problem. When a site is timing out during connection or the response, the SoapWrapper (and actuallty SoapClient itself) have never been able to figure out if exceptions thrown are thrown because of site errors or timeouts – except for through the error message.

With the new fix, a different exception will be produced under very specific circumstances: If the SoapClient throws an exception, based on error code 2 (E_WARNING), and the initial request time has exceeded the timeout configuration (from WrapperConfig) the exception is considered timeout instead of code 2. In such cases, the exception will be rethrown with code 1015 instead – but keep the error message produced by during the soap request.


A major update for DOM Documents

DOMDocuments has always been of interest for netcurl, especially since we use those features to fetch data for RSS feeds. The most recent fixes to handle DOM data with netcurl will now become available. However, there may be a continued integration with Laminas here to furthermore make requests more stable.

Below, you can see what’s been updated.

    Release Notes - PHP_NETCURL - Version 6.1.5
  • [NETCURL-338] – Docblock classes are not properly defined
  • [NETCURL-330] – Allow manipulation of SSL Verification settings
  • [NETCURL-335] – PHP 8.1 Tests
  • [NETCURL-339] – Use xpath to fetch rendered elements
  • [NETCURL-340] – xpath automation of the otherwise manual handling
  • [NETCURL-341] – Separate DOMHandler from GenericParser
  • [NETCURL-343] – Try to verify soap timeouts.
  • [NETCURL-345] – Remove SSL verification configuration for older PHP

RSS Feed is no longer in beta state

Documentation about the /rss resource can now be found here!

Tornevall Networks has, for a while now, been running a RSS feed agent in a kind of beta mode. This period has been used to safely make sure that the services are really properly running, fetching data and provides the data correct in the feed. So far, the flaws has been very few so it is considered no longer a beta testing.

We are also monitoring RSS-feeds, which may seem a bit contra productive. However, there are purposes for this too. Amongst a few, this makes it possible for us to get a compiled view of multiple sites that handles the same kind of categories. For example, if you have several RSS-feeds for Marvel content, this makes it also possible to merge those feeds into one.

Furthermore, we are also monitoring sites where there are no RSS-feeds available. You can read about the feeder above, at the first link. We also keep track of the total feed agents helping collecting data and the status at

To get a full list of RSS feeds currently available, you can read it in json, instantly from the url below. If you want to add a new feed to this monitor feel free to contact us via the page Contact.

DNSBL – – DNS Update: Moving resolvers

All secondary DNS servers for is currently being updated. Secondary services will from now on be hosted via Linode. As we are dismounting some internal DNS servers, this is one step in that progress. A second purpose of this change is also to make resolving faster worldwide.

The primary DNS, which is also currently the one that handles listings/delistings will be moved into a multi-address server, which means there are at least three entry points to it.

Changes amongst our DNS services, our beloved Stockholm Service shuts down in the end of 2023

The service that relies in runs an older version of OpenVZ which will reach an end of support 2023-12-31. Therefore, we will prepare to transfer this service elsewhere, probably already during this summer. If your DNS services depends on this, make sure you’re no longer using it.

The work has recently also started to migrate to a new master DNS. This work was finished today, which means that the API (v3) as of today communicates with a DNS that has closer reachability.

Taking a step forward

It has been a while since we touched api’s but this weeken we took a small step forward to replace an old API package. Instead of staying in a sphere of self maintained system, we’re about to try to run entirely over a Lumen instance. One of many reasons is the needs for, for example, a very long time planned data-to-rss-transformation system. This also means that we probably will deprecated the basic authentication system in a near future and start using JWT instead. For the DNS business, this may be a huge advantage in how data entries are handled in the editor.

To be continued…

Tornevall Maintenance and DNS updates

As our hosting conditions is about to radically change, the decision has been made to push away some of our DNS services. The services moved to Linode can not be used as recursive services. We’ve also completely removed the “microweb”-services, since they are practically empty and no longer necessary.

This is what’s happened during this weekend:


  • Relocated to Linode DNS.
  • Removed service in JP


Linode replacement


  • Relocated to Linode DNS
  • Removed service in NL


Linode replacement

Deprecating APIv3 for APIv4 – Rebooting the API

Tornevall Networks has plans to deprecate v3.x of the current TorneAPI-package. One of many reasons is that many functions are still bound to the netcurl 6.0-series – one other reason is an upcoming RSS-interface. There are also efficiency issues within the API that has been a problem. Not publicly but for internal perfomance. The first plan was to go APIv4, but instead there could be a major change – a reboot. Version 3 will remain in place, to handle DNS requests until there’s a new stable.

With this deprecation change, the DNSBL will got itself a major issue: Removals are now forced. This also means that a full removal procedure will be sent to the DNS even if the requested IP address is not confirmed listed.

Do not send delisting requests as comments

Tornevall Networks are closing most of the comment functions at TorneAUTH and this page, as the comment fields mostly are used as spam. Usually the comment fields has been acting honeypots for stupid bots, but it generates more problems than it helps. Amongst 2000+ spam comments, there’s a few that is requesting delists. It is, and has never been recommended, to use comments as a helpdesk. So instead, if you’re here for delisting – go directly to or send a proper mail to via the contact forms instead.


Update October 2021:

We STILL don’t actively read comments regarding delisting!