Some requests not using data compression (Accept-Encoding)

[mboelen]

Seeing in our logs that SimplePie is trying to get the feed. That goes well.

Then it follows with two requests. Both are blocked, as we don't allow uncompressed requests (Accept-Encoding).

Is the handler that pulls in the / URL and the favicon using a different set of options (HTTP protocol is different as well)?

2024-04-18T18:12:43+00:00 200 1.2.3.4 "GET /feed/ HTTP/2.0" 21552 "https://linux-audit.com/feed/" "FoF SimplePie/1.5.6 (Feed Parser; http://simplepie.org; Allow like Gecko) Build/20230917075900" TLSv1.3/TLS_AES_256_GCM_SHA384 0.000 .
2024-04-18T18:12:43+00:00 426 1.2.3.4 "GET / HTTP/1.1" 16 "-" "FavIcon/1.0 (Caching Utility; ; Allow like Gecko) Build/20160424000000" TLSv1.3/TLS_AES_256_GCM_SHA384 0.000 .
2024-04-18T18:12:43+00:00 426 1.2.3.4 "GET /favicon.ico HTTP/1.1" 16 "-" "FavIcon/1.0 (Caching Utility; ; Allow like Gecko) Build/20160424000000" TLSv1.3/TLS_AES_256_GCM_SHA384 0.000 .

[jtojnar]

That sounds like that is an issue with a SimplePie fork used by http://feedonfeeds.com/, which looks pretty dead.

I just tried with current SimplePie version (1.8.0) and the following example fetched the feed successfully:

<?php
declare(strict_types=1);
require_once __DIR__ . '/vendor/autoload.php';

use SimplePie\SimplePie;
$url = 'https://linux-audit.com/feed/';
$parser = new SimplePie();
$parser->set_feed_url($url);
$parser->init();
foreach ($parser->get_items() as $item) {
    var_dump($item->get_content());
}

[jtojnar]

FavIcon/1.0 (Caching Utility) definitely has nothing to do with SimplePie.

[jtojnar]

Looks like this fork based on the SimplePie version and the presence of Caching Utility: https://github.com/RomanSixty/Feed-on-Feeds

[mboelen]

Thanks @jtojnar for checking this out. I saw the 'FoF' but did not had a clue what it was. With your reference it makes sense that this is the project you listed. Strange that they mention SimpliePie so clearly and did not take the time to put up correct references to their own project.

I say we close this, as it clearly something outside this project. Thanks again!