[kovidgoyal]

Repeating myself one last time. The economist has moved to using statistical fingerprint based blocking. Any changes you make to the recipe will cause it to work *for some time* until enough people use the change, at which point it will stop working again. The *only* way to fix this robustly is to use a browser engine that is impossible to statistically isolate from regular browsers. As I said above one possibility for that is camoufox. If and when I find the time to finish its integration with calibre this can be re visited until then you can keep making endless tweaks to the recipe to have the download work for yourself personally, such as changing the user agent or the browser stack etc. But any and all such changes will not work if they are used for the builtin recipe which is used by large numbers of people thereby providing an easily detected signal. For a while we got away with using the endpoint used by the economist android app, but since last week the economist has blocked that as well.