Alternatives to CURL, WGET

Depends what you want to do, and why - you could implement a ban based on user-agent, that's the easiest way, but it won't stop a determined "scraper", but then little will.

It may be that enforcing referrer checks could achieve what you want as well.

Google certainly doesn't scrape with a curl-ush or wget-ish useragent, so it shouldn't affect that.

What web server are you using? Why are you trying to achieve this? These answers whill help us help you :)

The page you are redirected to says "You are not authorized to access this page!".

This is little more than a guess but I think that they are doing IP dependent content restriction and your laptop is in an allowed location while your server is not.

I tried the same URL myself and got the 302 redirect from two different places in the UK and one in France. I got a connection timeout from an Amazon EC2 server.

Oddly, they are using a 302 redirect to the error page rather than simply serving the error page with an appropriate HTTP response code, such as 403 or 401.