We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seeing in our logs that FoF SimplePie is trying to get retrieve our RSS 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 .
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Seeing in our logs that FoF SimplePie is trying to get retrieve our RSS 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)?
The text was updated successfully, but these errors were encountered: