Re: "406 not acceptable" errors with LWP::UserAgent::get

Seems the main thing it doesn’t like is the agent. Your code gave me the same error, even tweaked and pruned down until I swapped the agent for something that isn’t, apparently, blacklisted.

use 5.10.0;
use LWP::UserAgent;

my $ua = LWP::UserAgent->new;
$ua->agent('DomoArigato/3.0');

my $url = 'http://makeoursmarvel.com/feed/podcast/';

my $response = $ua->get($url);

say $response->is_success ? "OK!" : $response->as_string;

__END__
OK!
[download]

Comment on Re: "406 not acceptable" errors with LWP::UserAgent::get Download Code

Replies are listed 'Best First'.
Re^2: "406 not acceptable" errors with LWP::UserAgent::get by thomas895 (Deacon) on Aug 18, 2020 at 00:34 UTC
Usually to get around these kinds of blocks the easiest way is to set the user agent string to be the same one your browser uses -Thomas "Excuse me for butting in, but I'm interrupt-driven..."	[reply]
Re^3: "406 not acceptable" errors with LWP::UserAgent::get by Your Mother (Archbishop) on Aug 18, 2020 at 01:14 UTC
Disagree in the main. :P People blacklist agents, not whitelist, and a one-off for an agent that is NEVER abusive to a service is less likely to get crapcanned than one that shares a (base) name with 30% of the traffic.	[reply]
Re^3: "406 not acceptable" errors with LWP::UserAgent::get by jimhenry (Acolyte) on Aug 18, 2020 at 20:18 UTC
Thanks for the replies. I tried setting the agent to the user-agent string used by my current version of Firefox and had no trouble. (I'm still not sure why I was getting a 406 error for this podcast instead of a 403 Forbidden error, which I was getting on a number of podcasts with the default agent of "libwww-perl".)	[reply]
Re^4: "406 not acceptable" errors with LWP::UserAgent::get by Your Mother (Archbishop) on Aug 18, 2020 at 23:57 UTC
You can of course do whatever you want but I encourage you to use a unique agent name and version for your script; maybe even a less whimsical one than my original suggestion. :P I meant to expand on this and forgot. It’s more transparent—I’d argue more honest—better metrics for the host, and being a good netizen, from an API standpoint, is better for everyone and, I believe, reflects well on Perl compared to some other more, uh, mercenary communities. Update: response codes are at the discretion of the host code and webserver. They are frequently not particularly sensible.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks