Closed phpmoli closed 2 years ago
We block some user agents, and curl is one of them. Please use a different user agent.
The problem above is not with the blocking, the problem is that the blocking http return does not give a valid .rss content back, so all the poorly written rss clients go dumbfounded when they get a .html or anything else than a valid .rss back in the http body. The solution would be to:
edit: curl was just used for the sake of the example, as it is the simplest way to make a http request in linux.
Expected behavior
All rss feed urls should always return a valid xml, never-ever an html document, because that break rss feed reader clients, they cannot parse html, they expect a valid xml. Instead in case of http 500 or 429, return an empty body, if the rfc allows that.
Actual behavior
Feed urls return a html document and http 403 status code. Opening a feed url in a browser runs the javascript and redirects to the actual feed contents. It looks like Cloudflare DDoS protection? Maybe the feed urls should be exempted from the protection? When a client is malicious, return http 429.
Steps to reproduce the problem
In a command line prompt run the command:
curl https://www.apkmirror.com/apk/google-inc/feed/
The result will be: