Closed openminded-oscar closed 4 months ago
The headers changed, so you can try changing those to match what was going over the wire in 2.5.0 I don't have this issue, but i work from an ip address that does not query those urls over and over. You can try using a VPN, that might help. There's nothing else i can do here.
The urls like https://www.bbc.com/news/world-us-canada-68987314 was working with url-metadata v2.5.0 and returning page preview.
Looks like the issue can be related with deprecated npm 'request' http client replacing. After that it is getting 403 response status.
How do you think, can we do something with it?